Troubleshooting
Apian Labs Relay provides trace timelines, normalized errors, and webhook events to help you debug delivery issues. This guide walks through the most common checks when a message does not behave as expected.
Confirm test mode rules
Apian Labs Relay starts in test mode with destination allowlisting and conservative limits. Ensure the destination is allowlisted and the workspace is in the correct mode before sending live traffic.
Check message status
Fetch the message status first to see whether it was accepted, delivered, or failed. If the status is failed, move to the trace timeline to see which provider caused the failure.
Review the trace timeline
Trace events show provider attempts and the normalized error category. Look for repeated retryable errors or cooldown triggers that indicate provider instability.
Validate webhook ingestion
If you rely on webhooks, confirm signature verification and log rejected events. A missing or invalid signature will prevent downstream processing.