November 4, 2026 · Ahmed · More by Ahmed
Get Workflow Run Data: Flow's Single-Run Limit
Shopify Flow's Get workflow run data action reports on one run only. Here's how it differs from shop-wide error alerts and validation stops.
On March 24, 2026, Shopify shipped a batch of new "Get data" actions for Flow, including Get workflow run data. The name invites a reasonable assumption: a way to query automation health across a shop. The documentation says otherwise — this action retrieves data for exactly one workflow run, the run it's embedded in, with no filter fields to request anything else.
What the action actually returns
Get workflow run data takes no configuration fields at all. Placed anywhere in a workflow, it returns: the run's id and legacyResourceId, retryAttemptCount, startedAt (UTC), a triggerEvent object (id, source, triggeredAt), and a workflow object (id, legacyResourceId, name, tags, url, version). That's useful for making a single workflow retry-aware — for example, escalating only once retryAttemptCount crosses a threshold — but it is not a list of other runs, past or present.
There's a gotcha for scheduled automations: used inside a Scheduled time trigger workflow, there's no store or app event that started the run, so the trigger-event data Flow normally populates isn't there. A cron-style workflow built on this action for monitoring purposes will come back with gaps in exactly the fields you'd expect it to fill.
Shop-wide failure visibility is a different mechanism
If what you actually want is to know when any workflow in the shop fails, Get workflow run data isn't the tool — that's handled by a separate, older pairing: a workflow started by the Workflow error occurred trigger, running the Send Shopify alert for errors action. Its three identifying fields — Workflow ID, Workflow Name, and Workflow version — are hidden, auto-populated by the trigger, and can't be edited. You can't manually wire this alert to an arbitrary workflow; it only reports on whatever failed workflow triggered it.
Failing a run on purpose is a third thing entirely
The third piece, Fail workflow run, isn't about observability at all — it's how you make validation logic visible in Flow's run history. It takes one required field, a failure message, and when it fires the workflow stops immediately: any later actions or conditions don't run, even ones in a different conditional branch. Shopify's own example is an order-created workflow that fails the run when an order exceeds $10,000 USD without a manager-approval tag, so the failure — and the reason — shows up directly in Run history.
Put together, these three actions solve different halves of the same problem. Get workflow run data makes a single workflow aware of its own retry history. Workflow error occurred plus Send Shopify alert for errors gives you shop-wide failure alerts, wired automatically rather than configured by hand. Fail workflow run turns a business-rule violation into a visible, logged failure. None of them substitute for the others, and none of them add up to a cross-workflow monitoring dashboard — that still has to be built outside Flow if you need it.