debug-message

Diagnose a Hyperlane message delivery failure by providing the message_id or explorer_url to inspect origin and destination explorer data. This surfaces the message status, identifies relayer retry reasons, and determines the root cause across domains.

Debug stuck Hyperlane messages by inspecting relayer logs to identify retry reasons and failure modes. Correlate these logs with explorer data across origin and destination domains to pinpoint delivery failures and determine the root cause.

Hyperlane gas estimation issues occur when destination gas limits are insufficient. Analyze explorer data and relayer logs to verify gas settings, identify the failure mode, and determine if adjusting gas parameters or reattempting delivery is required.

Yes, provide a message_id to start a diagnostic session that surfaces the Hyperlane message status. It analyzes explorer data and relayer logs to identify delivery failures, gas estimation issues, or validator delays and recommends actions.

Fix Hyperlane message delivery failures caused by recipient contracts by inspecting error fields in explorer data and relayer logs. Identify the revert reason, update the recipient contract logic, and reattempt the message delivery.

Validator delays affect Hyperlane message processing by preventing relayers from submitting required signatures to the destination domain. Diagnose these delays by inspecting explorer timestamps and relayer logs to determine if delivery is awaiting validator quorum.