Troubleshooting
Diagnose pending, failed, partial, or unexpected operations without repeating actions blindly.
Use this page after an operation was submitted but its final state is pending, failed, partial, or inconsistent with the displayed balances.
Preserve the evidence first
Stop submitting actions to the affected wallets or launch.
Record the page, action, network, launchpad, approximate time, and public wallet addresses.
Open Activity and save the matching entry or transaction hash.
Compare Proxima with the relevant explorer and classify the result as pending, failed, partial, or finalized with an unexpected balance.
Choose the recovery path
| Observed state | First safe action | Do not do yet |
|---|---|---|
| Pending | Wait for a final explorer status | Repeat the transaction |
| Failed with no state change | Recheck balance, network, recipient, and prerequisites | Change several settings at once |
| Partial | Identify exactly which wallets or batch indexes completed | Resubmit the full selection |
| Finalized, balance looks wrong | Check asset, decimals, address, and network independently | Trust a stale table value alone |
| Automation unexpected | Review trigger, scope, mode, and latest activity | Recreate the rule before diagnosis |
A transaction is pending
Open the explorer from Activity when available. Confirm that a transaction was submitted, then wait for a final status. Refreshing the page or wallet table does not cancel an on-chain transaction.
An action failed
Recheck only the prerequisites relevant to that action:
- native balance for the action and network fees;
- active network and launchpad;
- source and recipient addresses;
- supported settings for the selected launch;
- existing funding, activity, or automation conflicts.
If no transaction was submitted and no balance changed, correct the demonstrated prerequisite and try once. If a transaction exists, verify its result first.
Only some wallets executed
Treat the operation as partial. Compare Activity, explorer transactions, and wallet balances, then create a recovery selection containing only wallets that still need the action.
Escalate with useful evidence
Provide the network, launchpad, page, action, approximate time, public wallet addresses, transaction hash or activity entry, exact error text, and a screenshot with secrets removed.
Return to Verify an Operation after any recovery action.