Aerodrome finance Incomplete Swaps and Retry Conditions

A Revert Unwinds the Swap's Token Movements

A transaction-level revert rolls back the swap's contract changes, including token transfers within that transaction. A route crossing several pools does not leave its earlier swaps settled when the entire transaction reverts.

Execution still consumes gas. A lower native-token balance after a failed transaction can therefore reflect network costs without indicating a completed trade. Compare the transaction's asset movements and fee record before treating the balance difference as missing swap proceeds.

A separate approval transaction remains effective even when the later swap fails.

Repeating every preceding action can create an unnecessary approval transaction, while assuming the swap succeeded can leave the intended exchange unfinished. Identify which transaction failed before deciding what to repeat.

Receipt Details Resolve an Incomplete Display

The receipt for the actual swap distinguishes execution success from failure. Match its hash, sender, and network to the attempted trade. An approval receipt can show success without proving any exchange occurred.

Successful Execution

A receipt status of 0x1 indicates successful execution. Inspect the operation and token transfers to confirm the output asset reached the intended recipient. An unchanged interface balance warrants reconciliation with those records, rather than another swap. Also check the token contract address: a matching symbol does not establish that two balances represent the same asset.

Open full-size image

Confirmed Failure

A receipt status of 0x0 indicates failure. The execution error or trace can explain the cause, although the receipt's status field alone cannot. No receipt means the outcome remains unresolved at that endpoint; it does not establish a revert or justify a replacement trade.

Should a Pending Swap Be Submitted Again?

A pending swap should not prompt a separate submission while the original transaction can still execute. Another transaction with a different nonce can become a second trade.

For a conventional wallet transaction, the nonce identifies its position in the account's transaction sequence. Wallets supporting replacement can attempt to speed up or cancel a pending transaction using the same nonce. Cancellation competes with the original transaction and takes effect only if its replacement confirms first. A replacement confirmation, rather than the cancellation request itself, resolves that uncertainty.

Preserve the original hash when the interface loses track of progress. A missing result from one endpoint can reflect indexing or connectivity problems. Waiting for a reliable status avoids turning a reporting delay into duplicate execution.

The Minimum Output Controls Execution

A protected exact-input swap includes a minimum acceptable output amount in its transaction parameters. The quote can change before execution, but the submitted threshold remains part of that transaction.

Aerodrome's standard exact-input router functions revert when their calculated output falls below the submitted minimum. Slipstream's exact-input functions also check output against a minimum. These checks enforce the minimum against the router's calculated output; they do not promise the earlier displayed quote or account for every token transfer fee. A custom call bypassing a check does not inherit its protection.

Slippage tolerance commonly expresses the permitted reduction relative to a quote. If the quote is Q and the tolerance is the fraction s, the corresponding minimum is Q × (1 − s), subject to token precision and rounding. Review the actual minimum the transaction submits, especially after refreshing the quote.

Balance and Allowance Failures Need Different Repairs

Available tokens and spending permission are separate prerequisites, so correcting one does not necessarily repair a transfer failure.

Spendable Balance

The connected account needs enough of the input token for the requested amount. Assets deposited in a liquidity pool or held in a lock do not count as its spendable token balance. Check the account and network before changing the trade size; a balance elsewhere does not satisfy this transaction's transfer.

Permission for the Actual Spender

An ERC-20 allowance authorizes a particular spender to transfer a particular token from its owner. An approval for another contract does not cover the selected spender. Compare the current allowance with the requested input amount before approving again. Increasing the trade size or changing the spender can alter that requirement, even when an earlier approval succeeded.

Expired Deadlines Require New Transaction Terms

A deadline check rejects execution after the timestamp supplied with the swap. Raising the gas fee on unchanged transaction data cannot extend that deadline.

A new attempt needs fresh transaction terms, including an acceptable deadline and output minimum. The deadline check stays the same, but each request supplies its own expiry timestamp. A quote refresh does not edit a transaction already signed or broadcast. Use the wallet's supported replacement process to replace a pending transaction; otherwise, resolve the original before submitting a separate trade.

A Fresh Quote With an Unchanged Output Rule

Network Charges Survive Failed Execution

Retrying adds another opportunity to incur network costs, even when the original swap transferred no tokens successfully. Price protection does not make failed execution free.

A contract revert does not refund gas already consumed during execution. Base transaction costs include execution and data-publication components. Their amounts vary, so the failed transaction's fee does not establish the next attempt's cost. Review the new fee estimate alongside the remaining native-token balance.

A higher gas limit permits more computation; it does not lower the output minimum or repair an invalid token transfer. Increasing transaction fees also cannot create liquidity. Match a fee adjustment to an actual fee or execution-budget problem rather than applying it to every revert.

Liquidity and Pricing Changes Affect Retry Terms

A refreshed quote reflects the route's available liquidity and pricing, which can differ from the state behind the failed attempt. Other trades and liquidity changes affect the output a given input can obtain.

Price impact describes the price movement the trade itself causes. Slippage describes a difference between the expected and executed result. A quote can already include substantial price impact before any additional movement occurs. Widening tolerance accepts a worse execution boundary; it does not improve that starting quote.

Reducing the input amount can reduce its impact on a pool, although the quoted result still needs review. A different available route can change fees, liquidity, and spending permissions. Compare the output for the intended input instead of assuming the route that avoids a revert also offers acceptable terms.

Unexpected Signing Requests Interrupt Recovery

A retry requires authorization for the intended trade, so an unexpected spender or recipient needs investigation before another signature.

A website error does not justify a transfer to a recovery address. A familiar-looking interface also cannot establish what a wallet request authorizes. Inspect the requested operation and allowance scope. If an earlier approval authorized an unintended spender, stopping new swap attempts does not remove that allowance; revocation is a separate onchain action.

The minimum-output check governs a swap's output. It does not validate an unrelated approval or protect assets exposed through another authorization.

When Does Another Attempt Make Sense?

Another attempt makes sense when the original outcome is resolved, the failure's cause has changed, and the fresh terms remain acceptable.

A confirmed revert with a corrected prerequisite supports retrying. A pending transaction supports waiting or managing its replacement. Successful delivery with a stale display supports reconciling the balance. An unexplained transfer restriction or unexpected authorization supports stopping until the cause is understood.

Refreshing a quote preserves the choice to decline changed terms. Automatically widening slippage exchanges a stricter output boundary for more permissive execution. When the new minimum falls below the amount you are willing to receive, waiting avoids authorizing that worse trade.