RelayLink Webhook Failure Runbook
Diagnose a silent RelayLink receiver from the account-page test through HTTP status, exact-byte HMAC, timeout, retry, automatic disablement, and recovery.
Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Diagnose a silent RelayLink receiver from the account-page test through HTTP status, exact-byte HMAC, timeout, retry, automatic disablement, and recovery.
Register several named receivers for one account when separate systems need the arrival signal. Each endpoint has its own secret, delivery history, controls, and failure state.
Send a signed webhook.test event from the account portal, inspect the exact body and headers, and prove your receiver is ready before a package depends on it.
Trace a missing RelayLink webhook from the account-page test through HTTPS reachability, signature handling, response status, retries, and automatic disablement.
Use the stable delivery id as a durable idempotency key, then separate receipt from processing so a crash does not lose work or repeat an external effect.