debug-message

Name: debug-message
Availability: InStock
Author: hyperlane-xyz

Diagnose unprocessed Hyperlane messages by analyzing explorer data and relayer logs.

72|602|Updated Dec 13, 2021

Search Tags:#logs #debug #message #gas #Hyperlane #explorer

Ready to run

npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill debug-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-message
Source: https://github.com/hyperlane-xyz/hyperlane-monorepo/tree/main/.claude/skills/debug-message
Command: npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill debug-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers diagnose why a Hyperlane message is not processed by analyzing explorer data and relayer logs to identify root causes such as delivery failures, gas estimation issues, or validator-related delays.

Core Features & Use Cases

Explorer-based diagnostics: Inspect origin and destination data to determine status and timestamps.
Relayer/log analysis: Correlate logs to identify retry reasons and failure modes across domains.
Actionable next steps: Provide guidance to fix recipient contracts, adjust gas, or reattempt delivery.

Quick Start

Provide a message_id or explorer_url to start a diagnostic session and surface the message status and root cause.

Frequently Asked Questions about debug-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why is my Hyperlane message not delivered to the destination domain?▼

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.

How do I debug Hyperlane relayer logs for a stuck transaction?▼

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.

What causes gas estimation issues for Hyperlane cross-chain messages?▼

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.

Can I use a message_id to find the status of a failed Hyperlane delivery?▼

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.

How do I fix a Hyperlane message delivery failure caused by a recipient contract?▼

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.

How do validator delays affect Hyperlane message processing across domains?▼

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.