Swap deadline passed? Check the transaction before retrying

A swap whose on-chain deadline has passed cannot execute through a router that enforces that deadline, so check the transaction status before retrying. Uniswap’s developer documentation describes the deadline as a timestamp guard; it does not cancel a transaction sitting in a wallet or waiting for inclusion.

Checking first can prevent a duplicate swap and show whether the failed attempt cost gas or still occupies your account’s transaction nonce.

Did the swap reach the blockchain?

Start with the transaction hash in your wallet and check it on the relevant chain’s block explorer. If the interface says “expired” but there is no hash, the app may have rejected a stale quote before broadcast; refresh the quote and review the new transaction details. A deadline in swap calldata only takes effect when a transaction reaches a contract that checks it.

If the explorer shows the transaction as pending, the deadline has not removed it from the network’s transaction queue. A wallet may offer a speed-up or cancellation using the same nonce, but either replacement must be accepted and included before it settles the original transaction. If the transaction was included and reverted with an expiry error, the nonce has been consumed and the swap did not complete. The failed execution still uses gas.

What should you verify before submitting again?

Once the earlier transaction is settled or confirmed never to have been broadcast, refresh the route and inspect the new quote. The deadline limits how long execution may wait; the minimum-output or maximum-input bound limits the permitted price outcome. Uniswap’s swap documentation treats those as separate protections, so extending a deadline does not refresh the quote or guarantee its price.

For a retry, check the details that determine what the contract will do:

• Confirm the chain, token addresses, direction, input amount and recipient.
• Read the quoted output and minimum received, or the maximum input for an exact-output swap.
• Check that the displayed route and quote are current, and that the deadline has not already elapsed before signing.
• Verify the wallet has enough native token for gas and that any required token allowance is in place.

For a closer look at how DCA changes the timing of swaps, the fuller sushiswap explainer covers the recurring-order mechanics. DCA changes when trades are submitted; it does not make an individual swap’s deadline a guarantee of execution.

Should you increase the deadline or slippage?

Change either setting only when the refreshed quote and the network conditions justify it. A longer deadline gives a transaction more time to be included, but also leaves its price bounds active for longer. A wider slippage tolerance may let a trade execute after a price move that would otherwise make it revert. Both choices can change the trade’s exposure, so retrying with the original bounds is the clearer default for most readers.

If a fresh transaction repeatedly expires, compare the quoted route and network conditions before changing those bounds. The useful distinction is whether inclusion was delayed or the market moved beyond the allowed output: a deadline addresses the former, while the swap’s amount bound addresses the latter. Check the status, refresh the quote, and submit again only when the displayed terms still match the trade you intend to make.