Recover an Arbitrum retryable whose automatic redemption failed
A successful parent transaction can create a child ticket without successfully executing its target call. Diagnose the ticket before asking a user to initiate another bridge transfer.
Follow the ticket and its execution attempts
Extract the retryable ticket identifier from the parent-to-child message using the chain’s bridge tooling. Locate the child creation receipt and the auto-redemption result separately. In the example, the target’s application effect has not occurred.
parent transaction: included
child ticket creation: succeeded
automatic redemption: reverted
Check ticket expiry and the cause of the revert. For a still-live ticket, anyone can request manual redemption with sufficient gas. Repeating an execution that violates a target contract condition will encounter the same application problem.
Observe the retry result
A transaction requesting redemption can schedule a separate child execution. Track that execution receipt and application events before crediting delivery. A fresh parent submission creates a separate message and can duplicate the intended action if the original later succeeds. docs.arbitrum.io Arbitrum documentation