Quote expired before signing: refresh or resubmit?

An expired quote should be replaced with a fresh quote from the application. The old output estimate and route may depend on conditions that no longer exist. Treat the refreshed quote as a new proposal to review.

Separate three different clocks

• Interface quote validity: how long the application considers its returned route usable.
• Transaction deadline: a condition enforced during contract execution, if present.
• Signature expiry: a limit on a permit or order authorization.

One clock can expire while another remains valid. Refreshing the screen does not automatically invalidate everything already signed.

MetaMask’s error guide describes an expiry error after waiting too long to confirm or submitting during quote refresh. This is one application’s diagnostic example, not a universal deadline for all aggregators.

Before requesting another signature

Determine whether the original swap was broadcast. If it is pending, check its status and manage it before creating a separate trade. If only approval completed, that permission may still be usable, although the new route might require a different verified spender.

Compare the new expected output, minimum received, fee, recipient and route type. A quote refresh can change more than the price number. Do not approve a different contract merely because the input and output ticker labels stayed the same.

If the application repeatedly presents already-expired requests, retain the time and detailed error for support. Repeatedly confirming faster is not a substitute for determining whether the application and wallet are using current transaction data.