Camelot exchange

Camelot exchange swap status determines when to wait or retry

Camelot exchange swaps need different responses when they remain pending, fail during execution or finish without updating the wallet display. Wait while a submitted transaction remains unresolved, unless your wallet supports an appropriate replacement or cancellation. Retry after a confirmed failure only when you've addressed its cause and accepted a fresh quote. If the transaction succeeded, inspect its output before signing again. A frozen interface alone doesn't establish which response fits your swap.

Updated on 10 Sep 2026

A Pending Transaction and a Completed Swap Have Different Outcomes

A submitted swap has a transaction hash, but that identifier alone doesn't establish execution. A successful transaction receipt records a completed contract call; the resulting token movements establish whether that call delivered the intended output. Check the selected network, account and transaction type before interpreting either record. A successful approval can otherwise look like a completed exchange.

A pending transaction has no completed execution result yet. A failed receipt records an unsuccessful attempt. Those states require different responses even when the interface shows the same unchanged balance. Receipt status describes the top-level call, so successful execution still needs to match the operation you intended.

When Should You Wait Instead of Retrying?

Waiting is appropriate while the original swap remains pending and you still accept its signed terms. Elapsed time alone doesn't establish failure. Check whether the network has included the transaction and whether the wallet identifies a replacement. If the original can still execute, a separately signed swap can create another trade rather than repair the first.

A wallet's supported speed-up option may replace a pending transaction using the same nonce, which identifies its position in the account's transaction sequence. Availability and fee requirements depend on the wallet and network. A cancellation also needs confirmation before you can treat the original as cancelled; the original transaction can win that race.

There isn't a useful universal waiting period for every stalled swap. The transaction's observable state determines whether waiting still serves a purpose.

Approval Delays Can Leave The Swap Unsubmitted

A token approval authorizes a spender to use an allowance. It doesn't itself exchange the tokens. When approval and swapping use separate transactions, an unresolved approval can leave the exchange waiting before swap submission. Identify which operation the wallet actually signed before diagnosing a stalled trade.

Allowance and Transaction Status

An allowance belongs to a specific owner, token and spender. An approval for another contract doesn't establish permission for the selected swap route. Repeatedly approving without checking those identities can add permissions without resolving the mismatch.

Approval Still Pending

A pending approval needs its own status check. Increasing swap slippage won't confirm that permission transaction or resolve its submission problem.

Approval Confirmed, Swap Missing

A confirmed approval leaves the exchange unfinished when no swap transaction follows. Review the quote again before authorizing the swap, especially after a delay.

What Must Change Before a Failed Swap Is Retried?

A retry needs a corrected failure condition and a fresh quote whose output you accept. Inspect the failed transaction's error before changing settings. A contract error can describe a price constraint, missing permission or another execution condition. The same generic failure label can conceal different causes, so repeatedly signing the same request provides little diagnostic value.

A top-level transaction revert rolls back the state changes made during that transaction's execution. Gas used by the failed transaction is still charged. A separately confirmed approval remains a separate operation. Distinguish those records before assuming that the failed swap removed its spending permission.

Open full-size image

Funding problems require a different correction. For a transaction that requires the account to pay native network fees, a sufficient input-token balance doesn't establish sufficient gas funds. Check the paying account on the selected network. Increasing slippage doesn't resolve that shortage.

A Fresh Quote Can Change The Acceptable Output

A fresh Camelot quote can differ from the quote that preceded the failure. Review minimum received, price impact and the exchange rate before retrying. Raising slippage tolerance permits a wider execution difference; it doesn't improve liquidity or guarantee success. If the resulting minimum output no longer suits the trade, waiting or stopping preserves that boundary.

Transfer-tax tokens need particular care. A tax can affect the amount available during execution, and compatible routing depends on the token and the pool that holds its liquidity. Camelot's tax-token guidance advises avoiding aggregator mode because it can charge the tax multiple times. An estimated-amount error alone doesn't establish a tax, since volatility can also produce that message.

Recovery Options and Their Effects on Transactions

Recovery choices differ in what they change and whether the original authorization remains live. Reading records changes no transaction. Replacement and cancellation require wallet support and successful network processing. A fresh swap creates another authorization, so it needs a resolved original state and its own acceptable terms.

When Should You Stop Signing and Investigate?

Stop signing when transaction records conflict, the error remains unexplained or the proposed output breaches your acceptable minimum. A successful receipt paired with a stale wallet display calls for balance reconciliation, not an automatic retry. Use the selected network's block explorer to check the output token's contract address, intended recipient and net amount received against the signed minimum output.

Repeated failures after unrelated setting changes indicate that the cause still needs diagnosis. Preserve the transaction hash and error text before dismissing the wallet notification. An error such as "Estimated XXX amount invalid. Check your slippage configuration" doesn't, by itself, establish that increasing slippage will solve the problem.