Check forced-inclusion eligibility for an Arbitrum delayed message
A parent-chain receipt for a delayed message is not the point at which anyone can immediately force it into the child sequence. Eligibility depends on the deployed SequencerInbox rules.
Use the original delivery record
Record the delayed message index, parent block number, timestamp and message fields from the parent-chain events. Inspect the target chain’s current force-inclusion configuration, including any applicable delay-buffer behavior.
message delivered to Delayed Inbox → waiting period → forceInclusion → child execution
For a chain requiring both a parent block and time threshold, reaching the time threshold alone may still produce a too-soon error. Calculate against the actual parent chain and use a read-only simulation of the intended forceInclusion call.
Confirm ordering before resubmitting
Check whether the sequencer already consumed the delayed message while you waited. Forced inclusion advances delayed messages in order. It does not guarantee a successful child application call; inspect the child receipt after the message enters the sequence. docs.arbitrum.io Arbitrum documentation