The automation is enabled, but a customer has not received anything? Inspect a specific event in history. Enabled describes the configuration; it does not mean every person qualified or an email was delivered.
Open the appropriate history
Select the rule in Automations and open Execution history. Start here to inspect events belonging to this automation.
Check the store, rule name, contact and event time. Similar names can hide different conditions and delays.
In this example, Open leads to the accepted message’s history, where you can check later delivery and activity. The skipped event says consent is missing; retrying cannot replace obtaining it. The waiting event does not yet have a sent email history.
Separate the stages
Waiting can concern timing, data, a limit or the channel. A queued message is not yet accepted by the provider. Acceptance for sending does not establish that the customer read it.
A click is another event. No click does not prove failed delivery, and attributed revenue in a report is not store profit.
Read the exclusion reason
Common causes include missing identity or consent, a newer purchase, a segment mismatch, an event before activation, changed settings or stale data.
For a cart, compare its last activity and later orders. For a product alert, check confirmation and the product change. For a follow-up, also inspect the first email.
Qualification preview examines up to 25 recent events without sending. It is not a complete report of all future recipients.
Prepare a useful example
Record the automation name, contact or event ID, expected time and displayed reason. Include the order or cart number where relevant.
Check store data, consent and sending hours. If the cause remains unclear, share these details with the support team using the contact below this article.

