Dropped swap with no replacement: when is retrying reasonable?

A dropped swap is not necessarily permanently cancelled. A node can remove a pending transaction from its local pool while another node still has it or later rebroadcasts it.

Etherscan’s explanation of dropped transactions explicitly notes that rebroadcast can return one to pending status. That makes “not found” weaker evidence than a confirmed same-nonce replacement.

Establish whether the old request can still matter

Check the sender’s confirmed nonce sequence and any replacement transaction. If the original nonce has been consumed, follow that confirmed result. If it has not, the old signed transaction may remain relevant, even when your current explorer does not show it.

Also inspect any application or private-submission status available from the service that accepted it. Public pending visibility is not complete.

Retry with a deliberate plan

If you still want the same action and its conditions remain valid, the wallet may support resubmission or replacement. If the old quote is stale, a new quote changes the decision. Do not create a second transaction with a later nonce while assuming the first is dead.

An explicit cancellation may be appropriate when you want to remove the original execution possibility, but it still requires confirmation and can lose the race.

Document the original hash, nonce and deadline before clearing any local activity. These details let support distinguish a transaction that was never accepted from one that disappeared from a particular provider’s view. Retry only after you understand which earlier authorization could still execute.