Shopify Flow Not Triggering? How to Find Out Why

"Flow isn't working" describes at least three different problems. The workflow never ran. The workflow ran and decided to do nothing. Or it ran, did something, and the result never showed up where you expected.

They look identical from the outside, and each has a completely different fix. So the first move isn't editing the workflow. It's finding out which of the three you're dealing with — and Flow already records the answer.

Open the workflow and check Run history. Everything below follows from what you find there.

If you're building a workflow for the first time rather than fixing one, start with Shopify Flow setup.

Flow's triggers, actions and plan availability change regularly. Confirm current behaviour in Shopify's own Flow documentation before relying on any specific detail here.

Run history lists every time the workflow started. What you see there tells you where to look.

No run for the event you expected. The trigger never fired. The problem is upstream of your logic: the workflow's status, the trigger you chose, or when the event happened. Go to the next section.

A run that stopped at the condition. The trigger worked perfectly. Your condition evaluated to false and the workflow correctly did nothing. This is the most common case, and people often misread it as "not triggering". Go to the conditions section.

A run where the action failed. The trigger and condition both worked, and the action step errored. Open the failed step and read the actual error text, not the status label.

A run where every step succeeded, but nothing happened. Flow did its job. The problem is further down the line — usually delivery, or another system that was supposed to act on what Flow did.

Test with a real record that should match. Place a test order or update a test customer, then check Run history within a few minutes. Runs aren't always instant, so give it a moment before deciding nothing happened.

If Run history shows nothing for your event, work through these in order. The first two catch most cases.

1. The workflow is off. Workflows save in an off state until you turn them on. Obvious, and still the most common cause — especially after editing, duplicating or importing a workflow.

2. It's listening for the wrong event. Order created and Order paid are different triggers and fire at different moments. So are fulfilment events, refund events and customer events. If you want something to happen when payment clears, a workflow on Order created will fire at the wrong time or act on unpaid orders.

3. The event happened before you turned it on. Flow reacts to events from the moment a workflow is active. It doesn't go back and process orders or customers that already existed. To act on existing records, use a scheduled trigger that retrieves them.

4. The order came from somewhere else. Draft orders, POS sales, imported orders and orders created by other apps don't always behave like storefront orders. A draft order, for instance, isn't an order until it's completed. Test with the order source you actually care about.

5. An app trigger lost its connection. Triggers from third-party apps depend on the app being installed, connected and permitted. Uninstall, reinstall or a permissions change can silently break them. See Shopify apps not working if the app itself is misbehaving.

6. Your plan doesn't include what the workflow uses. Some triggers and actions are limited to particular plans. Worth checking if a workflow was built on a different store or copied from a template — see Shopify plans and pricing.

If Run history shows runs that stopped at the condition, the workflow is doing exactly what you told it to. The condition just doesn't say what you meant.

AND versus OR. The single most common logic error. "Tag is VIP AND total over 200" requires both. If you meant either, the workflow will skip most orders.

Exact text matching. A condition checking that a value equals "wholesale" won't match "Wholesale" or "wholesale-uk". Use contains-style matching where the value can vary, and check the exact text on a real record.

Empty fields. A condition that checks a field which is blank on that record evaluates to false. Guest checkouts, POS sales and draft orders are frequent culprits, because they often lack a customer record or an email address.

Lists treated as single values. Tags, line items and collections are lists. Checking them requires any-or-all logic, not a simple equals comparison.

Numbers and currency. Comparing a total against the wrong currency, or against the subtotal when you meant the total, produces conditions that are technically valid and never true.

The fastest way to find it: take a record that should have matched, open its failed run, and check each part of the condition against that record's actual values. The mismatch is usually obvious once you're looking at real data rather than the workflow editor.

A workflow that ran for the first record and then never again is usually working as designed. Two patterns account for most of it.

A guard condition doing its job. A common and sensible pattern is "if the customer doesn't have tag X, do something, then add tag X". That prevents repeats. It also means the workflow will never fire again for that customer — which looks like a bug if you've forgotten the tag was the guard.

A trigger that only happens once per record. Customer created fires once per customer. Order created fires once per order. If you expected a workflow to react every time something about a customer changes, you need a trigger that responds to that change rather than to creation.

Less commonly: the workflow changed the very thing it was watching, so later events no longer match its conditions. If a workflow edits the same record that triggered it, check whether that edit is what stops it firing next time.

If Run history shows your workflow running and the email step is the part that fails, the trigger isn't the problem. The two usual causes are the action and the variable: Flow's Send internal email action is built for staff notifications rather than customer messaging, and Liquid copied from notification templates breaks because Flow uses the Admin API's camelCase field names. Both are covered step by step in Shopify Flow send email to customer.

If Shopify's own order notifications aren't arriving — confirmations and shipping updates rather than anything Flow sends — that's a separate problem, covered in Shopify email not sending.

Run history plus a test record solves most Flow problems in an afternoon. Three situations are worth handing over.

Workflows chained across several systems. Flow triggering an app, which updates something that triggers another workflow. When one link fails, it takes someone who can trace each hop — workflow automation experts, or specialists in Shopify Flow specifically.

Intermittent failures you can't reproduce. A workflow that works for some records and not others, with no obvious pattern, needs runs compared systematically — bug fixing and troubleshooting experts.

A store running dozens of workflows nobody fully understands. Built by different people over years, some overlapping, some fighting each other. Auditing and rebuilding that is a project in its own right. Development specialists by market: United States, United Kingdom, Australia.

How to vet: ask what they'd check first. If the answer isn't Run history, they're guessing.

Open Run history on the workflow that isn't working and find the record you expected it to act on. No run means you're looking at the trigger. A run that stopped at the condition means you're looking at the logic. A failed step means you're looking at the action.

That one distinction resolves most Flow problems faster than any amount of editing, because it tells you which third of the workflow to look at.

For chained workflows, intermittent failures or an automation setup that's grown out of control, browse workflow automation experts. Free matching, verified experience, no commissions.

Related guides on Shopify Flow and automation:

• Shopify Flow Send Email to Customer — when the workflow runs but the email step fails
• Shopify Flow Setup — building workflows from the start
• Shopify Email Not Sending? — when order notifications don't arrive
• Shopify Apps Not Working? — when an app trigger stops firing
• Shopify Plans & Pricing — what your plan includes
• Workflow Automation Experts — chained workflows and automation audits