Articles on: React Flow

Guidelines and Limitations

Guidelines and limitations


In this article:


React Flow plans differ in how many workflows you can keep active and how many runs are included each month. This article explains how workflows and runs are counted, what happens when you reach a limit, and which other limits apply, so you can choose the right plan and keep your costs predictable.


Workflows and runs


A workflow is a chain of a trigger, conditions and actions that automates a task in your store, for example "when an order is paid, tag the customer and send a thank-you email".


A run is one execution of a workflow. Most of the time, one trigger event is one run: when a new customer signs up, a "Customer created" workflow runs once.


What counts as a run


  • Each trigger event that starts a workflow is one run.
  • Each item returned by a Fetch step is a separate run. A workflow that fetches 500 customers uses 500 runs, plus one for the trigger.
  • Each item in a One-Shot workflow with Fetch resources is a separate run. The Runs counter shows the number before you start.
  • Tests don't count. Run Test with Simulate or Execute is free.


For details and examples, see How runs are counted in React Flow.


When you reach your monthly runs


Your workflows keep working after you reach the runs included in your plan. Each extra run is charged at your plan's per-run rate. Extra runs are charged during the trial period too.


  • The included runs reset on the 1st day of each month.
  • The subscription itself is billed every 30 days.


You can see the per-run rate of your plan on the Plans page in the app.


When workflows start and stop


  • A workflow works only while it's turned on. You can build and save it first, and click Turn on when you're ready.
  • An Automated workflow reacts only to events that happen after you turn it on. To process existing orders, products or customers, use a One-Shot workflow with Fetch resources.
  • When you turn off or archive a workflow, the delayed actions and fetches that haven't run yet are skipped.
  • "Updated" triggers (Order updated, Product updated, Draft order updated, Inventory level updated) need a stored value to compare with. For items that existed before the workflow, the first change only saves the value. To make the first change count, run Set observe data once (see the Observer article).


Delays


Add a Delay step anywhere in a workflow to wait before the next steps. Under Type, choose:


  • Minutes, Hours or Days: wait for a set amount of time.
  • Delay until: wait until a specific date and time.
  • Date and time from variables: wait until a date taken from the store data, for example a date in an order metafield.


Example: to email a customer 3 hours after an order is cancelled, choose the trigger Order cancelled, add a Delay of 3 Hours, then add Send email.


When you test a workflow with Run Test, delays are skipped so you see the result right away.


Plans


  • Pay as you go: free to install. Up to 20 active workflows and 100 runs per month included. Extra runs are charged per run.
  • Starter, Standard and Professional: unlimited workflows, a larger number of included runs on each plan, and Shopify Functions. Extra runs are charged per run, at a lower rate on higher plans.
  • Unlimited: unlimited workflows and unlimited runs, with no overage charges.
  • Enterprise: custom terms for large stores, including custom pricing, dedicated infrastructure and a support model tailored to your operations. Contact our team to discuss it.


Starter and Standard include a 7-day free trial. All plans include unlimited triggers, actions and conditions, and 24/7 support.


For current prices and the number of runs on each plan, open Plans in the app or see the React Flow page in the Shopify App Store.


Other limits to know


  • Built-in email: up to 500 emails per day through the default React Flow sender. Emails sent through your own SMTP or Microsoft connector have no React Flow limit.
  • Run code: JavaScript (ECMAScript 2020), up to 50,000 characters, 70 seconds and 10 MB of memory per run. See the Run code technical guide.
  • Activity charts: a date range of up to 90 days.
  • Files: PDF content up to 20 MB (Shopify) or 25 MB (Google Drive); Transfer file from URL up to 5 MB.


For more cases and workarounds, see the article "What React Flow can't do, and workarounds".


Tips to use fewer runs


  • Combine workflows. Instead of five workflows that each start on "Order created" and check a different product tag, make one workflow with five conditions. Each order then uses one run instead of five.
  • Filter early. Add conditions before fetch actions when you can determine that further resource fetching is no longer necessary, reducing unnecessary runs.
  • Narrow your fetches. Use a query and Maximum number of ... in Fetch steps, and check the Runs counter before you save.
  • Turn off what you don't use. Archived and turned-off workflows don't use runs.
  • Test for free. Use Run Test while you build. Tests don't count as runs.


✔️ Next step


Check our articles to learn more about the app's functionality:


Updated on: 14/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!