Workflow Trigger ExtensionsWorkflow Trigger Extensions

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.

The trigger appears but never fires▾

Work through these in order:

  1. Is the switch on? Most field-level triggers are off by default. Check its switch on the Triggers page. 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 the Data sync section on the Triggers page.
  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.
  4. Is the broad trigger switched off? If you switched the resource's ... Update trigger off on the Triggers page, its events stop.
  5. Does it need a second permission? Order Shipping Address Changed also requires Customer Data Access.
A storefront trigger fires less than expected, or not at all▾

Storefront triggers are collected in the shopper's browser, so they are best-effort by design. Check, in order:

  1. Storefront Behaviour Access is granted and the trigger's switch is on. Nothing is collected until both are true.
  2. Consent. A shopper who has not given analytics consent is dropped in the browser and never reaches us. In regions where consent is opt-in, that is most traffic.
  3. Ad blockers and closed tabs stop the request. There is no retry.
  4. Storefront Cart Viewed only fires on the /cart page; a cart drawer never navigates there. Use a Custom Storefront Triggers for drawers.
  5. Out-of-Stock Variant Viewed only fires for the variant the page landed on, and only once the variant's inventory has been synced.

See Storefront triggers for the full list of what can and cannot be seen.

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 switch the broad one off. For storefront triggers, remember that Storefront Product Viewed and Out-of-Stock Variant Viewed fire on every product page view. See Choosing the right trigger.

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.