---
title: "Event history and troubleshooting"
description: "Use Event History to confirm a trigger fired, and work through the common reasons a trigger does not appear, does not fire, or fires too often."
canonical: "https://docs.workflow-trigger-extensions.app/event-history-and-troubleshooting"
---

# Event history and troubleshooting

**Event History** records every trigger this app fires, so you can confirm a workflow
was started and diagnose it when it was not.

## Reading the history

The list shows the trigger, the resource it fired for, the time, and the delivery
status. Click a row for the detail view: the full trigger name, the resource reference,
the timestamp, and any delivery error returned by Shopify Flow.

Use the filters to narrow by trigger type or status when you are chasing a specific
event.

## Troubleshooting

Select the symptom that matches what you are seeing.

### The trigger does not appear in Shopify Flow

The permission has not been granted. Open **Permissions** and grant the data access for
that resource, then reload the Flow editor. See [Permissions and data access](https://docs.workflow-trigger-extensions.app/permissions-and-data-access.md).

### The trigger appears but never fires

Work through these in order:

1. **Is the setting on?** Most field-level triggers are off by default. Check the
   relevant tab on **Settings**. Turning the Flow workflow on normally does this for
   you, so a trigger that is off usually means the workflow is off too.
2. **Has the baseline sync finished?** Change detection cannot report a difference
   before it knows the starting state. Check for the loading indicator on the Settings
   tab.
3. **Is the quota exhausted?** Check usage on **Home**. At 100% triggers pause until the
   period resets or you upgrade. Note that events which occurred while you were over the
   limit are **lost rather than queued**, and they leave no history row, so an empty Event
   History during a period of exhausted quota is expected rather than a fault. See
   [Plans and usage](https://docs.workflow-trigger-extensions.app/plans-and-usage.md).
4. **Is the broad trigger suppressed?** If you suppressed `... Update` on the first
   Settings tab, related events stop.
5. **Does it need a second permission?** **Order Shipping Address Changed** also
   requires Customer Data Access.

### The workflow runs but does nothing

Check Shopify Flow's own run history. If the trigger fired and Flow started the
workflow, the problem is in a condition or action step rather than in the trigger. The
app's Event History confirms delivery; Flow's history shows what happened next.

### It fires too often

The trigger is too broad. Switch from **Order Update** to a specific trigger such as
**Order Line Items Changed**, and suppress the broad one. See
[Choosing the right trigger](https://docs.workflow-trigger-extensions.app/choosing-the-right-trigger.md).

### A change was made by an app or import and did not fire

Bulk imports and app-driven writes do fire triggers, with two caveats: they are subject
to the same per-store rate limiting, so a very large batch is delivered over a period
rather than instantly, and if the batch exhausts your quota the remainder is not
delivered.

> [!NOTE]
> **Still stuck?** Have these four things to hand and the event can be traced end to end:
> your **store domain**, the **trigger name** exactly as it appears in Shopify Flow, an
> approximate **timestamp** of the change you expected to fire, and what **Event History**
> showed at that moment.