Resolve a pending or uncertain Spot trade
Trading · Troubleshooting · Recovery of existing Spot requests; checking status never authorizes a replacement transaction.
Keep one request identity, inspect its status and avoid duplicate signing or sending.
Reviewed: 2026-10-18
Before you start
- The account that owns the request.
- Its saved request reference or an entry in Your spot requests; a signature may not yet exist.
Expired review versus submitted transaction
An expired review cannot be newly confirmed. If nothing was submitted and no active unresolved request exists, use Requote to obtain a new review and inspect its costs again.
Transaction expiry after submission is different: it does not by itself prove nonexecution. If the recorded request has a signature, reservation or uncertain outcome, use its recovery panel instead of requesting a replacement.
- Open /markets/spot and find the existing entry in Your spot requests.
- Select it and read its status, signature and reason before editing the ticket.
- Only obtain a new quote when the old request’s authoritative state allows a new action; never use requoting as recovery for an unknown send.
Preserve the original request
Pending means the outcome is still being checked. An unknown result can mean a signature exists or a send started even if no success screen appeared. Keep the request identity and use Reload status; if the ledger itself fails, use its Retry or Reload read.
An unresolved expired transaction can retain its signature and reservation while history is checked. A history status without a full verified receipt may also remain held. The recovery page reads and reconciles the original—it does not re-sign or resend.
- Keep the same account and request open; preserve the non-sensitive request reference and any public signature.
- Use Reload status and inspect the reason and explorer link if present.
- If the read fails, retry the read later. Do not approve another wallet packet or submit another trade to free the reservation.
Chain execution and accounting are different
Confirmed or finalized execution can appear before finalized fee recognition and buyback/burn processing. Read Trade status and Fee recognition separately. A swap can be on chain while accounting is still pending.
Inspect the original explorer signature and refresh the original record. Do not trade again to trigger accounting, and do not treat a pending burn allocation as a completed purchase or burn. A missing balance refresh likewise does not negate the chain result.
Only use actions the request offers
Cancel this request is offered for an open request, not as a reversal of an in-flight or confirmed swap. Read the returned status after cancellation; an error is not confirmation that cancellation happened.
Dismiss is available only for eligible non-polling states. It clears the selected recovery view, not chain history, a completed trade or its financial record. Closing the page also does not cancel a send.
- If the request is open and you no longer want it, use Cancel this request and check the result.
- For in-flight or unknown states, continue status reads instead of looking for a reversal.
- Dismiss only when offered after reviewing the terminal result. Keep the reference if another issue remains.