investigate-stuck-messages

To investigate stuck relayer queue messages, query the relayer API to correlate retry data and fetch actual errors from GCP logs, which surfaces full message IDs and actionable steps for denylisting.

Provide a Grafana alert URL to automatically extract app_context and remote labels, driving the full stuck message investigation workflow across the relayer API, domain metadata, and GCP logs.

Yes, you can manually provide app_context and remote inputs directly to run targeted relayer queue investigations that fetch domain IDs, query the relayer API, and extract GCP log errors without an alert URL.

Extracting message IDs for denylisting involves querying the relayer API to fetch domain IDs, filtering messages by recipient, and correlating retry data with GCP log errors to surface full message identifiers.

Yes, relayer queue investigation supports both Grafana alert URL and manual workflows across mainnet3, consolidating relayer API data, domain metadata, and GCP logs to present retry counts and full message IDs.

Find the root cause of stuck prepare messages by correlating relayer API retry data with actual errors fetched from GCP logs, which surfaces specific error sources and full message IDs for denylisting.