Email logs

Where: Communications → Email Logs

What was actually sent, to whom, and whether it succeeded.

Why this is the first place to look

When someone says they did not receive an email, there are two very different explanations:

1. It was never sent — a rule was off, a condition was not met, a template was not configured.
2. It was sent and did not arrive — a delivery or spam problem.

The logs tell you which. Every other diagnosis is guessing, and the two problems have nothing in common.

Filtering

Filter by status, mail type and source, and page through the results.

Filtering by Failed is the useful health check. Run it occasionally during a live event rather than waiting for complaints — failures cluster, and a batch of them usually shares one cause.

Reading an entry

Each log records the recipient, the type, when it was created, its status, and a Log ID. An Email Preview shows what was actually sent.

The preview is the authoritative record of what the participant received, which is more useful than the template — the template is what you meant to send.

Common patterns

Nothing logged at all for a message type. It was never triggered. Check the automation rule and its conditions.

Logged as failed. It was attempted and rejected. Check the address, and whether the event could be resolved at send time.

Logged as sent, participant says no. A delivery problem. Check spam, check the sender address, and ask them to look for the sender name rather than the subject.

A cluster of failures at one time. Something changed then — a branding change, a credential change, or a bad address list.

Non-standard addresses

Some entries are flagged where the recipient address is outside the usual pattern. Worth a glance if you are chasing a delivery problem for a specific person.

Keeping the record

Treat the logs as the evidence trail for anything disputed — a participant certain they were never told about a deadline, a sponsor asking whether an announcement went out.

It is a far better answer than recollection.