The swap failed on slippage: what should change before retrying?

A slippage-related revert often means the transaction’s output protection worked: the route could no longer deliver the minimum you authorized. The right response is to reassess the quote, not automatically remove that protection.

Compare the decision you signed with the market now

Record the original quoted output and minimum received. Request a fresh quote for the same token contracts, chain and amount. Check whether the new expected output is already below the old minimum.

Uniswap documents slippage limits as a failure condition. An aggregator can use different route construction, but the practical issue is still whether the execution satisfies its encoded amount limits.

Hypothetical example: you accepted a minimum of 990 units but a fresh quote now estimates 980. Raising tolerance would permit an outcome you previously ruled out. Decide whether you actually want that trade at the new level.

Look beyond ordinary price movement

• Large input relative to available liquidity can worsen output.
• A long wait before inclusion can make the original quote stale.
• Transfer fees or unusual token behavior can change what reaches the route.
• Public transaction exposure can create additional execution risk.

Where token fees are involved, confirm that the route supports that token behavior. An extremely wide tolerance is not a general compatibility fix.

If you choose to retry, use fresh transaction data and deliberately set the minimum result you accept. A smaller amount or another supported route may offer a different trade-off. If neither meets your requirements, a reverted trade is preferable to authorizing an outcome you do not want.