Skip to main content
Uruguay Can

News from across crypto

How to Retry a Wormhole NTT Transfer and Resume It

A Wormhole NTT transfer can be retried when rate-limit capacity refills; complete a queued transfer after its delay, or submit a new one if it reverted.

Uruguay Can Editorial

How to Retry a Wormhole NTT Transfer and Resume It

You can retry a Wormhole Native Token Transfer (NTT) when the relevant rate limit has enough capacity again: complete it if it was queued, or submit a new transfer if it reverted.

  • An outbound revert leaves no queued transfer to complete.
  • A queued transfer becomes eligible after its configured delay.
  • A destination-side queue has its own eligibility check.

If you use Monad bridge to move supported assets between Monad and Ethereum, the NTT status still tells you whether to wait on the source or destination chain. For background on Monad bridge NTT rate-limit behavior, see what happens when a transfer hits the limit.

Source status tells you whether to queue or resubmit

Your source transaction status determines the next step: a revert means you must start a new transfer, while a queued transfer already has a place in the outbound queue. Queueing depends on the transfer’s shouldQueue setting in the NttManager; if queueing was off, a transfer that exceeds outbound capacity reverts.

Rate limits replenish over a configured duration, and that setting varies by deployment. Twenty-four hours is the documented default, not a universal countdown that begins when you click transfer. Capacity refills over time, so the wait depends on the available capacity, the transfer amount and the deployment’s settings.

Say you try to send more than the source chain’s available outbound capacity, and the transfer is queued. Find its queue entry and eligibility time in the app or transaction details. After the configured delay expires, complete it with completeOutboundQueuedTransfer. Trying earlier can fail because the transfer is still queued.

Destination status determines whether delivery needs completion

If the source transfer completed but your tokens have not arrived, check whether the destination NTT Manager placed the delivery in its inbound queue. Inbound limits are configured per source chain, and a queued delivery can be completed with completeInboundQueuedTransfer once it is eligible.

  1. Identify the source and destination chains, then inspect the source transaction or queue status.
  2. If an outbound transfer is queued, check its eligibility and complete it after the configured delay.
  3. If the transaction reverted, wait for enough outbound capacity to refill, then submit a new transfer. Confirm the amount and destination before signing again.
  4. If the source completed, check the destination queue and complete the inbound transfer when eligible.

That status check gives you the right next action: complete the existing queued transfer, or make a fresh attempt after capacity returns.