# Reading the Flow Activity Log

> Source: https://primemoq.app/help/automations/flow-activity-log
> Collection: Automations
> Updated: 2026-08-26

Every event Prime MOQ sent to Shopify Flow, or did not send and why, plus a per-rule breakdown of what is actually reaching your workflows.

**Short answer.** The Automations page's activity log lists every trigger sent to Flow and every action call received back, with a status and a reason whenever something did not go through. Clicking View details on a rule's row opens that rule's own summary, covering sent against skipped counts, the biggest reason events are not reaching Flow, and the products, orders and customers involved.

## Key takeaways

- The table shows your most recent 50 events. Refresh pulls the latest.
- Most skips are expected behaviour rather than a fault.
- The Customer column shows Guest or Customer only, never a name or email.
- The rule detail view covers a rolling 30 days and includes a daily trend chart.

## Before you start

- Event sending turned on, or every row reads as skipped for that reason.

## 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.

## FAQ

### How far back does the activity log go?

The table shows your most recent 50 events. The per-rule detail view covers a rolling last 30 days, which is the window the tiles and the trend chart are calculated over.

### Why does one block show once when the shopper clicked several times?

Repeat blocks from the same shopper within a short window are deduplicated into a single event, so one frustrated customer does not consume your hourly cap or start several identical workflow runs.

### What does Rejected mean, as opposed to Error?

Both mean Shopify's Flow platform did not accept the event. The Reason column carries the specific cause, and that is the field worth reading rather than the status on its own.

### Can I export the activity log?

Not currently. It is view only inside the app, and the per-rule detail view is the summarised version to work from.

### Nothing appears at all. What should I check first?

The send toggle on the Automations page, then your plan. Those two produce the first two reasons in the table above, and between them they explain most completely empty logs.

**Best for:** Confirming your workflows are actually receiving events, and working out why a specific rule's automation is not firing.

**Applies to:** Pro plan