Statuses and troubleshooting
Practical recovery steps for wallet, order, transaction, price, and escrow issues.
Solana reference
This chapter covers Solana. For the main Robinhood Chain network, see the Robinhood guide. Wallets, token addresses and settlement mechanics are specific to each network.
Start with the correct page
Price panels refresh automatically, but use Refresh on an individual market to reload its open offers. Use Refresh activity for dashboard data. Open a wallet-held trade page to reconcile its transaction status; a stored dashboard snapshot alone does not establish finality.
The market directory is a bounded recent listing view, not an exhaustive historical search. The current directory loads up to 200 recent markets. Your dashboard also uses bounded recent history. A missing old item in a summary is not proof that an on-chain transfer never happened.
Wallet and launch problems
| Issue | What to do |
|---|---|
| Wallet not detected | Install the supported wallet extension, or open the site in its mobile wallet browser. The flow needs an injected provider. |
| Connect the wallet that created this transaction | Switch to the initiating maker/taker or operation wallet. A launcher or fee recipient is not automatically a trade signer. |
| Wallet request rejected | No approval was granted. Reopen the action and review it before trying again. |
| Token or extension not supported | Use the exact token mint, not a wallet, token-account or pool address. Original SPL tokens and Token-2022 mints with no extensions or only MetadataPointer, TokenMetadata and TransferFeeConfig are supported for wallet-held trading. Other mint extensions and Token-2022 account extensions other than ImmutableOwner are rejected. Token-2022 funded escrow is unavailable. |
| Website and social links required | For a team launch, provide complete HTTPS website and social URLs. Do not include URL credentials. |
| Image too large or wrong format | Use PNG, JPEG or WebP under the input limit; crop or reduce it if browser encoding cannot fit the upload limit. |
| 50-market limit reached | Use an existing market owned by this wallet; the current limit is enforced for new registrations. |
Offer and price problems
| Issue | What to do |
|---|---|
| Market comparison unavailable | The pair, quote-currency reference or fresh price is missing. Review your fixed price manually; do not treat an absent comparison as at-market. |
| Chart missing or delayed | Use the direct DexScreener chart link. A token may not have an indexed pair, or the external embed may be blocked. |
| Price or revision changed | Refresh the offer and approve its current fixed terms. An old preparation cannot silently accept a new price. |
| Another trader reserved or changed this order | A competing request won. Refresh before preparing another fill. |
| An active fill must finish or expire on chain | Open View fill and allow reconciliation. A reserved offer cannot be repriced or filled again. |
| Use no more than the supported decimal places | Enter a plain decimal quantity within the token mint precision. |
| Trade size is too small or too large | Adjust the fill so quote value and the remaining order both meet the supported bounds. |
| Maximum active orders reached | Resolve reserved fills and cancel old open offers; pending funded deposits can also count toward the cap. |
Signing and settlement problems
| Issue | What to do |
|---|---|
| Insufficient tokens or quote balance | Use the correct wallet and supported associated token account. Keep the required balance until settlement. |
| Not enough SOL for network costs | The taker needs SOL even when the order is quoted in USDC, because network fees and account rent are paid in SOL. |
| Transaction changed or signature invalid | Do not submit edited transaction bytes. Return to the original trade or prepare a fresh one after the old attempt is safely resolved. |
| Awaiting maker | The taker signed, but the maker must approve the same transaction. Open/share the trade link. |
| Submitted or confirming for longer than expected | Inspect the public signature and refresh the trade. RPC failure or delay is not proof of cancellation. |
| Blockhash or signing window expired | Let reconciliation verify non-settlement, then review a fresh attempt with a new blockhash. |
| Finalized transaction failure | The exchange did not partially settle; network fees may have been charged. Review the failure and balances before retrying. |
Escrow-specific problems
| Issue | What to do |
|---|---|
| Funded escrow is not activated | Use the available wallet-held path. Do not send a manual deposit to a guessed program or wallet. |
| Market escrow not activated | When network-level escrow is enabled, the market owner must separately activate the on-chain market. |
| Order changed before fill | Another fill/cancellation may have changed its cursor. Refresh and prepare again using current state. |
| Funding is pending | A prepared deposit is not an open funded offer. Open the operation page and wait for finalized verification. |
| Expired order still has a balance | Expiry blocks fills but does not auto-refund. The maker must submit recovery, or a technical caller can use the contract expiry instruction. |
| Completed order still has token-vault rent | Use maker cancel/reclaim to close the token vault. Market/order state rent stays allocated. |
| Frozen token account | Only the issuer’s freeze authority can thaw it. Sidelot cannot override a freeze to trade or refund. |
| Program/account terms mismatch | Stop and preserve the operation link. Do not bypass the check or deposit elsewhere; contact support with public identifiers. |
Order state reference
| Stored order state | Meaning |
|---|---|
| open | Has remaining quantity; expiry, balances and settlement mode still determine whether it can be filled. |
| reserved | A wallet-held trade attempt has reserved it. |
| filled | The entire quantity has settled. |
| cancelled | The remaining order was cancelled. |
| expired | Expiry has elapsed/reconciled. Funded assets may still require a refund transaction. |
| pending_funding | A funded order is awaiting verified deposit finality. |
| funding_failed | The funding operation failed or expired without finding the funded order. |
Transaction and operation state reference
Wallet-held attempts use awaiting_taker, awaiting_maker, submitted, confirming, finalized, failed and expired. Escrow operations use awaiting_signature, submitted, confirming, finalized, failed and expired. A finalized funding operation creates an open order; a finalized partial fill can leave an order open. Do not confuse the operation state with the order state.
A wallet-held order can retain an open stored label in history after its separate expiry timestamp passes. The expiry check still prevents a new fill. Network signing windows use block-height evidence, not an exact fixed number of seconds. See Solana confirmation and expiry.