# Troubleshooting

Investigate pending, failed, partial, or unexpected operations and check their status before deciding what to do next.

> Source: https://proxima-docs.pages.dev/other/troubleshooting/
> Language: English
> Content version: sha256:5a460d9a8606939796c5d35b06be1f413c635a57ada3752404037bd5d1fff8be

Start here if an operation is pending, failed, partial, or inconsistent with the displayed balances, or if the interface behaves unexpectedly.

Video to come**Troubleshooting**

## Check service status

Check the [Proxima status page](https://status.proxima.tools/) for incidents or maintenance before reporting a bug. You can also open it from the service-status indicator in Proxima’s bottom bar.

## Diagnose the result

1.  Stop submitting the same action to the affected wallets or launch.
2.  Open [Activity](https://proxima-docs.pages.dev/settings/activity/) and find the matching entry or transaction hash.
3.  Compare the Proxima status, explorer result, and affected balances to identify what completed.

> **Warning**
> 
> Never expose a private key, seed phrase, API key, or authentication secret in a screenshot, error report, or support request.

> **Warning**
> 
> A failed batch or multi-wallet action can contain successful transfers or trades. Its overall status is not proof that every wallet remained unchanged.

For wallet funding, inspect the existing task’s funded destinations and available **Rescue** or **Cancel** action before creating another plan. [Fund Wallets](https://proxima-docs.pages.dev/wallets/fund-wallets/)

## Report a problem

If you still need to report a problem, follow [Report a problem](https://proxima-docs.pages.dev/other/report-a-problem/) to submit it from Proxima.