Debugging Notification Failures with Sent Log Details

Log Details provide a granular breakdown of each notification instance, detailing processing time frames, payload components, raw provider responses, and the definitive status of your message delivery path.

This view is essential for debugging delivery failures and optimization loops when creating routing pipelines for an Event.

To access the Log Details inspector pane, navigate to the Sent Logs panel and click directly on any individual transaction row.

Log Metadata Sections

Each log entry breaks down into dedicated tracking tabs providing high-fidelity transparency for auditing:

Trace – Core chronological routing timeline across internal systems.
Summary – Snapshot overview of event variables, timing, and provider profiles.
Placeholders – Variable payload bindings matched to the client API schema request.
Content – Rendered visual layout strings transmitted downstream.
Response – Synchronous API acknowledgment codes returned by provider endpoints.
Delivery – Asynchronous webhook statuses mapped directly back by carrier receipts.

Lifecycle of a Notification

Every transaction features individual progression stages dictated by target carrier mechanics. Reviewing the capabilities of each delivery pathway ensures clarity when verifying metric performance and system event properties.

Channel	Submitted	Delivered	Read / Open	Clicked	Deleted / Dismissed
SMS	Yes	Yes	No	Yes	No
WhatsApp*	Yes	Yes	Yes	Yes	No
Email	Yes	Yes	Yes	Yes	No
Slack	Yes	No	No	Yes	No
Teams	Yes	No	No	Yes	No
Discord	Yes	No	No	Yes	No
InApp	Yes	Yes	Yes	Yes	Yes
Push (SDK)	Yes	Yes	Yes	Yes	Yes

* WhatsApp Tracking Constraint: The tracking ecosystem will update your dashboard state to Read exclusively if the target consumer has enabled Read Receipts inside their native mobile client configurations.