Flow Failure Alerting on Shopify: Build the Watcher or Buy One?
Flow failure alerting is a CUSTOMIZE, because Shopify ships no store-wide setting that tells you when a workflow breaks. The documented pattern is a dedicated workflow built on the Workflow error occurred trigger, designed to run only once per workflow version within 30 days. Run history disappears after 14 days, so the watcher has to push every failure somewhere you keep. Budget $5,000–$15,000 (Deploi estimate, illustrative).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's Workflow error occurred reference: the trigger starts a workflow when workflows fail during execution, and it is designed to run only once per workflow version within 30 days (verified Sep 2026). Read the workflow monitoring page: workflow runs are stored for 14 days after a run has completed, after which the run is removed from the system and is no longer available, with no Plus versus non-Plus distinction anywhere on the page. Across the Flow help pages reviewed, no store-wide notification preference, no digest, and no per-workflow alert setting appears anywhere; building a second workflow that watches the first is the pattern Shopify documents. Searched the App Store's workflow-automation category: MESA is the closest verified vendor at 5.0★ across 153 reviews, and its monitoring covers the automations you build inside MESA rather than the ones running in Flow. No listing reviewed reads Flow's run history or alerts on a Flow failure.
- Reference scenario
- $20M–$200M GMV · Shopify Plus · 20–60 live workflows covering tagging, routing and customer messaging · an ops team that currently learns about failures from support tickets
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under 5 workflows, all low-stakes | WAIT | Five workflows applying tags and internal notes fit on one screen. Checking the dashboard weekly costs less than any watcher you could build. |
| 5–20 workflows, some customer-facing | CUSTOMIZE | One watcher workflow and a notification action take an afternoon and cover the whole library. There is no cheaper reliability spend on this list. |
| 20–60 production workflows | CUSTOMIZE | At this size the 30-day dedup window matters: the trigger reports the first failure of a workflow version, not the tenth. Pair the watcher with a daily run-history export before the 14-day window closes. |
| Plus organization running workflows across several stores | BUILD | Flow is store-scoped, so each store needs its own watcher and each reports separately. One external monitor consuming every store's failures is the only way to see the portfolio at once. |
What Flow Failure Alerting Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | An alert on the day of failure turns a week of manual reconciliation into a ten-minute fix, because the affected records are still a short list. |
| Customer experience | High | Failed notification and fulfillment workflows reach the customer as silence, so the alert is what stops a support ticket from being your monitoring. |
| Data & insight | High | Exported run history gives failure counts per workflow over months, turning reliability work into a ranked list instead of a guess. |
| Revenue — indirect | Medium | Workflows driving win-back offers and restock alerts stop earning the moment they break, and nothing in the revenue report names the cause. |
Spend ceiling: The watcher is an afternoon of work, so spend the budget on what happens after the alert: routing to one owner, exporting run history past 14 days, and heartbeat checks for workflows that stop firing without ever raising an error.
What buying enables (top apps)
- + Run history and error handling built into a second automation platform, for the workflows you move there
- + MESA's 7-day free trial makes that comparison cheap before any migration (verified Sep 2026)
- + Vendor-maintained connections to tools that have no Flow tasks of their own
- + A dashboard someone else keeps working as Shopify's APIs change
What building additionally unlocks
- + An alert the first time any workflow version fails, across the whole library, from one watcher
- + Failure history that outlives Shopify's 14-day run retention and lives in your warehouse
- + Heartbeat checks that catch workflows which stopped running entirely, which no error alert reports
- + One consolidated view across every store in a Plus organization, which store-scoped Flow cannot give you
Find Your Verdict in 3 Questions
Would a workflow failing silently reach a customer or corrupt a record?
Yes: Go to question 2.
No: Your verdict: WAIT — a weekly look at the dashboard is proportionate for a handful of tagging workflows.
Do you need the real count of failures, not just the first one per workflow version?
Yes: Your verdict: CUSTOMIZE — build the watcher and add a daily run-history export before the 14-day window closes.
No: Go to question 3.
Do workflows run in more than one store in your organization?
Yes: Your verdict: BUILD — one external monitor consuming every store's failures, because Flow is store-scoped and each watcher reports alone.
No: Your verdict: CUSTOMIZE — one watcher workflow on the Workflow error occurred trigger covers the whole library.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | The watcher workflow is an afternoon inside Flow; the full pattern with an external log runs an estimated 2–4 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | A workflow-automation subscription bills monthly forever; a watcher built on Flow's own trigger adds no subscription line. | ||
| Maintenance & upgrades | The watcher is small and stable, but every store in an organization needs its own copy kept in step. | ||
| Switching & exit | Alert routing configured in a vendor dashboard does not export; a watcher workflow and an exported run log stay with your store. | ||
| Risk | |||
| Vendor risk | No App Store listing reviewed alerts on Flow failures at all, so the buy lane is a category adjacent to the problem rather than aimed at it. | ||
| Security & compliance surface | Pushing failure payloads to an outside monitor means order identifiers leave Shopify; keep the payload to identifiers and reason codes. | ||
| Platform-deprecation exposure | The watcher depends on one documented trigger and one action, which is about as small a platform surface as a build can rest on. | ||
| Value | |||
| Fit to requirement | The requirement is knowing that a Flow workflow failed, and only a Flow-native trigger sees that event. | ||
| Time to market | Both lanes land within days, because the watcher is one trigger, one condition and one notification. | ||
| Performance & scale | The 30-day dedup window means the watcher reports a failing version once, which is quiet at scale but hides repeat volume. | ||
| Data ownership & AI-readiness | An exported run history keeps failure data past 14 days, so you can rank workflows by real failure counts instead of memory. | ||
| Focus & opportunity cost | Few builds this small change the day-to-day this much, since the alternative is finding out from a customer. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Flow | Native — Per july 2026 research. Shopify's own automation layer — the WAIT option to exhaust first | Free at entry volumes; scales with volume (verified Sep 2026) | Catching the first failure of every workflow version, once a watcher is built on the trigger |
| MESA: Workflow Automation | Live — 5.0★, 153 reviews; 7-day trial on all paid plans. A multi-step automation platform that reaches further across your stack than Flow's own actions. Useful for orchestrating a bulk job's surrounding steps, though it is an automation tool rather than a bulk-editing one, so it does not remove the need for a real bulk lane. | Basic $12/month; Flex $29/month; Pro $99/month; Unlimited $299/month (verified Sep 2026) | Relocating critical automations onto a platform that ships its own monitoring |
| Workflow automation and notification apps | Category — The App Store's workflow-automation category is where merchants look first. Those listings build automations and send notifications about store events. None of the listings reviewed reads Flow's run history or raises an alert when a Flow workflow fails, which is why the category cannot close this gap. | Free to roughly $300/month across the category (illustrative) — confirm on each listing | Moving work off Flow entirely, rather than monitoring what stays on it |
| Watcher workflow plus run-history export | Build lane — One workflow on the Workflow error occurred trigger that names the failed workflow and posts it to your incident channel, plus a scheduled export that captures run history before the 14-day window closes, plus a heartbeat check for workflows that stopped firing entirely. Small, and it is the pattern Shopify documents. | $5,000–$15,000 one-time plus roughly 15–20% a year in upkeep (Deploi estimate, illustrative) | Any store where a silent workflow failure reaches a customer before it reaches the ops team |
The Build Path
- The watcher workflow itself: One workflow on the Workflow error occurred trigger, which starts when workflows fail during execution (verified Sep 2026). Route the failed workflow's name and the run details to the channel your ops team already watches. Start here, because it covers the whole library at once.
- Push failures out of Shopify: The Send HTTP Request action, available on the Plus, Advanced and Grow plans, posts the alert to your incident tool. Flow waits a maximum of 30 seconds for a response code, and the action can retry a 5XX or 429 for up to 24 hours (verified Sep 2026), so a monitor that blips does not lose the alert.
- Export run history before day 14: Workflow runs are stored for 14 days after completion, then removed from the system. A daily scheduled export gives you failure counts over months rather than a fortnight, which is what turns a hunch about a flaky workflow into a ranked list.
- A heartbeat for workflows that stop firing: The error trigger reports runs that failed, not runs that never started. A scheduled check that expects at least one run per period for each critical workflow catches a disabled trigger or a broken condition, which is the failure mode no error alert can see.
- Effort band
- $5,000–$15,000 build — Deploi estimate (illustrative); lands in the $10–25K contact-form band. A single watcher plus alert routing sits at the bottom; watchers across every store in an organization, with an exported run log and heartbeat checks, sits at the top
- Typical timeline
- 2–4 weeks (Deploi estimate, illustrative): the watcher itself is an afternoon, and the rest is the export, the heartbeat checks and agreeing who responds
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $750–$3,000/yr (Deploi estimate, illustrative) to keep alert routing current, add each new store's watcher and prune noisy checks. Flow itself stays free.
- What you own — and what you take on
- You own: the watcher, the alert routing, the exported run history and the heartbeat definitions for every critical workflow. You take on: keeping a copy of the watcher in each store, and responding to what it finds, which is the part that actually changes outcomes.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $8,000–$20,000 (rebuild on another platform) | $5,000–$15,000 |
| Years 1–3 (recurring) | $3,600–$10,800 (subscription) | $2,250–$9,000 (maintenance) |
| 3-year total | ≈$11,600–$30,800 | ≈$7,250–$24,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: MESA's Pro tier at $99/month (verified Sep 2026) plus a project to rebuild the critical automations there, at illustrative agency rates, since no listing monitors Flow itself.
- † Build path: one watcher workflow, alert routing, a daily run-history export and heartbeat checks on ten critical workflows; three-year horizon; single store.
What the Sticker Price Hides
On the buy path
- — No App Store listing reviewed watches Flow itself, so the buy lane really means relocating the automation, not monitoring it
- — A second automation platform splits the library, and nobody can answer why a record changed without opening both
- — Metered plans price retries and repeated runs the same as successful ones
- — Rebuilt automations still need their own error handling, so the reliability work follows you across
On the build path
- — The 30-day dedup window means one alert per workflow version, so repeat failures look quieter than they are
- — A watcher that alerts everyone alerts nobody; route to one channel with a named owner
- — Workflows that stop firing entirely raise no error, which is why the heartbeat check is not optional
- — Roughly $750–$3,000/yr in upkeep (Deploi estimate, illustrative) plus a watcher copy in every store
What Merchants Say
Ops leads describe learning about failures backwards: a customer asks where their shipping notice went, and by the time anyone opens Flow the run has already rolled off.
Automation reviews cluster on quiet failure: the workflow is still listed as active, the dashboard looks normal, and only a manual spot-check reveals it stopped doing anything weeks ago.
If You Change Your Mind Later
If you bought and outgrow it
Alert routing and rebuilt automations configured in a vendor dashboard leave as documentation rather than configuration, so a switch means re-expressing both. Export the vendor's run history before cancelling, because it is the only record of what fired during the period you paid for.
If you built and want out
Nothing is stranded: the watcher is one workflow in your own store, and the exported run history sits in your warehouse. Moving to a monitoring product later starts from a list of which workflows actually fail and how often, which is exactly the information that makes such a purchase sensible.
When This Answer Changes
We're watching for:
- ▸ A store-wide or organization-wide failure notification setting in Flow (none documented as of September 2026)
- ▸ Any change to the 30-day dedup window on the Workflow error occurred trigger, which decides how much repeat failure you can see
- ▸ Flow run retention moving beyond 14 days, which would remove the need for a scheduled export
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Does Shopify alert you when a Flow workflow fails?
Not on its own. Shopify provides the Workflow error occurred trigger, which starts a workflow when workflows fail during execution, and you build the notification from there. No store-wide failure setting appears across Shopify's Flow help pages. One watcher workflow covers the entire library, and it reports once per workflow version within 30 days.
How often does the Workflow error occurred trigger fire?
Once per workflow version within 30 days, by design. The window is scoped to a version, so the watcher reports the first failure of that version rather than every failure. A workflow breaking forty times in a week produces one alert. Pair the trigger with an exported run history if you need the real failure count.
How long does Shopify keep Flow run history?
14 days. Shopify's monitoring page states that workflow runs are stored for 14 days after a run has completed, after which the run is removed from the system and is no longer available. Any question asked in month two has no data behind it. A scheduled daily export is the only way to hold failure history longer.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Build one workflow on the Workflow error occurred trigger and route it to a single channel with a named owner
- Include the failed workflow's name in the alert, so triage starts without opening Flow
- Schedule a daily export of run history, since Shopify removes runs after 14 days
- Add a heartbeat check for each critical workflow, because a workflow that never runs raises no error
- Re-publish the watcher in every store in the organization, then keep the copies in step
- Review the exported failure counts monthly and fix the top two offenders
If you're going with BUILD
- Stand up one external monitor that accepts failure events from every store
- Send alerts out with the Send HTTP Request action, available on Plus, Advanced and Grow
- Store failure history for at least a year, well beyond Flow's 14-day retention
- Define per-workflow heartbeat expectations so a stopped trigger pages someone
- Add each new store to the monitor as part of its launch checklist
Official Docs & Sources
- Workflow error occurred trigger — Shopify Help Center
- Monitor workflow runs (14-day retention) — Shopify Help Center
- Troubleshoot Flow workflows: transient and permanent errors — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Flow Loops or Bulk Operations for Hundreds of Shopify Records?
Flow's Get data actions run on lists of up to 100 items, so a For each loop cannot sweep a large catalog. Catalog-wide edits need a real bulk lane.
Your App Has No Flow Connector: Build the Bridge or Wait?
Only an app's own developer can ship its Flow tasks. Outbound automation needs just Send HTTP Request; inbound needs a bridge app from $29/month (verified Sep 2026).
Flow Workflow Retries on Shopify: Build Your Own Safety Net?
Flow retries transient errors like step timeouts and 5XX statuses, and never retries permanent ones. Critical workflows need their own error branches.
Flow Wait Steps or a Lifecycle Tool for a 90-Day Win-Back?
Shopify Flow allows 40 wait steps per workflow and 90 days of total waiting. A 90-day win-back needs a lifecycle platform; shorter operational waits stay in Flow.
Should You Build or Buy Site Search on Shopify?
Site search on Shopify splits by catalog size: native to ~1,000 SKUs, buy in the middle, build at big-catalog, search-led scale.
Would you know today if a workflow stopped running?
We build the watcher, route alerts to one channel with a named owner, and export run history before Shopify removes it at 14 days.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. The absence of a store-wide alert setting reflects every Flow help page reviewed in September 2026; confirm on Shopify's current reference before you assume it still holds.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.