Reading the table
| Column | What it shows |
|---|---|
| Name | Which trigger or action fired |
| Direction | Trigger, meaning Prime MOQ to Flow, or Action, meaning Flow to Prime MOQ |
| Status | Sent, Accepted, Skipped, Error or Rejected |
| Rule | Links to the rule involved, when there is one |
| Reason | Why an event was skipped, errored or rejected. Blank on success |
| Customer | Guest or Customer, meaning whether the shopper was signed in |
| Detail | Opens that rule's summary, when one is available |
Every reason you might see
| Reason | What it means |
|---|---|
| Flow emission is off for this shop | The send toggle on the Automations page is off |
| Shop is not on Pro | Sending needs the Pro plan |
| Duplicate within the dedupe window | The same shopper hit the same block again too soon to count separately |
| Over the hourly trigger cap | You are past 100 events in the hour |
| Rule has no maximum quantity set | A reset action needs a maximum to reset against |
| Rule no longer exists | The rule an action targeted has been deleted |
| Shopify rejected the payload | Shopify's Flow platform returned an error for this event |
| Request to Shopify failed | A network-level failure reaching Shopify |
| Validation failed | The event's data did not pass validation before sending |
| Unexpected internal error | A Prime MOQ side error, so nothing was sent at all |
The first four are normal operation. A log full of "duplicate within the dedupe window" means the deduplication is doing its job, not that events are being lost.
Investigate one rule
Find the rule's row and click View details.
Read the top tiles: sent to Flow, skipped or errored, and customers affected.
Read the "why it is not firing" section. It names the single largest reason events for this rule are not reaching Flow, as a percentage, which is usually enough to end the investigation on its own.
Scroll to products or orders involved, shown for the trigger types that carry that data, and the daily trend chart.
Common mistakes
- Expecting a name or email in the Customer column. It shows Guest or Customer. Identifying detail, where it exists, is in the detail view's Customers section and only for that period's top contributors.
- Expecting View details on every row. It appears only on rows tied to a specific rule. An action with no rule context has nothing to summarise.
- Assuming customer emails are always available. Without Shopify's protected customer data approval you see a customer ID where an email would otherwise be.
- Reading Skipped as broken. The send toggle being off, a duplicate inside the dedupe window and being over the hourly cap are all by design.