Delivery Troubleshooting Lab

Your test email is missing? Find out where it stopped.

Don’t resend it repeatedly right away. Confirm the address first, then check the send job and provider response, and finally verify inbox polling and message rendering.

Start troubleshooting

Waiting for input

Complete all four items on the left first

The diagnosis identifies the first layer worth checking and provides the next piece of evidence. It does not pretend to read your sending system directly.

Copy the complete recipient address used for this test.
Keep the send time, message ID, and response code.
Record whether you can see the subject, HTML, and plain-text body.

Five-layer evidence chain

Work outward from the easiest step to verify

Find observable evidence at each layer before moving to the next. This helps prevent an address issue from being mistaken for a template problem.

Address layer

Copy the address again from the current page. Check that everything before and after @ is intact and that the temporary inbox is still within its countdown. After changing addresses, don’t continue using the old token or recipient address as the test target.

Evidence: complete address and validity period

Job layer

Confirm that the business action actually triggered an email job rather than merely adding an item to a pending queue. Check environment variables, queue consumers, template selection, and recipient parameters.

Evidence: job ID and execution logs

Delivery layer

Review the response returned by SMTP or the email provider. Acceptance only means the next hop received it; it does not mean the message reached the inbox. A rejection code usually points you in the right direction.

Evidence: message ID and response code

Retrieval layer

Wait for one polling cycle, then refresh manually. If other messages appear in the same inbox, the issue is more likely with one message or upstream delivery than with the page connection.

Evidence: refresh time and message count

Body layer

If the list shows a subject but the details are empty, check html_body and text_body separately. An HTML template error, oversized remote resource, or unsafe script does not mean the email failed to arrive.

Evidence: original subject, sender, and body fields

Quick diagnosis

Different symptoms call for different priorities

Symptom	Check first	Check next
No emails arrive at all	Address validity and send job	Provider response, DNS, and rate limits
Only one template fails to arrive	Template job and recipient parameters	Content policy and attachment size
Messages appear in the list, but details are empty	HTML/plain-text fields	Template syntax and content isolation
Delivery is noticeably delayed	Queue wait time and provider events	Inbox polling and network status

Minimal reproduction

Reduce complex business logic to one comparable email

Send a new address a fixed subject, one plain-text sentence, and a unique event ID. If the minimal email arrives, gradually add back HTML, images, attachments, and business variables.

Record these details

Test environment and submitted version

For example: staging / commit hash

Trigger time and message ID

Use UTC consistently or specify the time zone

Address, subject, and result

Redact tokens; never paste verification codes into tickets

Return to a real inbox test

Create a clean address and complete the minimal reproduction

Keep the evidence from this send, then use a temporary inbox to verify the subject, time, and body.

Open temporary email