Flow runs

A run is one pass through a flow, started by one trigger event, such as one delivered order. Each flow's page lists its runs, and each run shows the path it took through the flow, step by step. Test runs and past orders you enroll are runs too.

Navigate to Settings → Flows⁠ and open a flow to see its runs.

• Each trigger event starts a run in every live flow on that trigger, even when a Filter ends the run at once. See Flows.
• A run follows the version of the flow that was live when it started, even after you publish changes
• Every email and event a run sends, test sends included, is listed in Outbox. Review requests also show in Request tracking, except those sent to a webhook.

A test run runs a flow once, on a real order, review, or member, or on sample data. Its sends are real, but they go to test destinations: emails go to your own address instead of the customer's.

1. Navigate to Settings → Flows⁠
2. Click ... in the flow's row
3. Select Trigger test run
4. Select what to run the test on, such as an order in Order
5. Optional: Select Current draft or Live version in Version
6. Click Start test run. The test run opens.

What you can run a test on depends on the trigger:

• Order triggers: An order from your store. When your workspace has no orders yet, Mock order uses sample data.
• Review triggers: A product review or a company review from your workspace
• Upload and loyalty triggers: A member in Member, with the event's details, such as the tier or the expiry date. Cevoid simulates the event and doesn't change any points, tiers, or rewards. Dates must be in the future.

Current draft runs the last saved draft, so save your changes first. It's offered while the draft differs from the live version.

Test runs show in Runs with a Test badge. Your workspace can start 20 test runs an hour.

A test run keeps the flow's timing, so an action after a Wait is scheduled for when the wait ends. In a test run, you can send it now.

1. Navigate to Settings → Flows⁠ and open the flow
2. Click the test run under Runs
3. Click the Wait step that's waiting
4. Click Skip wait. The next step sends now instead of at its scheduled time.

A scheduled action in a test run shows Continue now instead, which sends it right away. Live runs always keep the flow's timing.

Enrolling past orders runs a live flow once over orders from a date you choose, as if each order were fulfilled or delivered now. It's for live flows on Order fulfilled or Order delivered.

1. Navigate to Settings → Flows⁠
2. Click ... in the flow's row
3. Select Enroll historical orders
4. Set Enroll orders since to the earliest order date to include. Orders from that date through today are included.
5. Optional: Select a market in Market. The default is All markets.
6. Click Start enrollment

• What's included: Orders placed in that period that are fulfilled, or delivered for an Order delivered flow. The dialog shows how many match before you start.
• Timing: Each order runs through the whole flow, waits and filters included, counted from when you start the enrollment
• Progress: Historical runs, below your flows on Settings → Flows⁠, shows each enrollment with its market, status, and results. To stop one, click Cancel there, or select Cancel bulk enrollment in the flow's row menu.
• Review requests: Customers who have already reviewed are skipped, so import your existing reviews first. See Send requests to past orders.

Runs, on a flow's page, lists the flow's runs, newest first. Click a row to open the run.

A run's page shows the flow as the run follows it. The path the run took is highlighted, and each card shows its step's state, such as Completed, Waiting, Scheduled, or Skipped.

1. Navigate to Settings → Flows⁠ and open the flow
2. Click the run under Runs. Run details opens next to the canvas.

When a step stopped the run, a notice says which step and why, such as Stopped by Filter with the condition that didn't match, or that an action wasn't sent, with the reason. Timeline lists each step on the run's path with its time, starting at Event received. A waiting step counts down to when it continues. To look at another run or attempt, select it in the menus above the canvas.

Each step in an open run has its own details: click its card to see its status, when it started and finished, and for an action, its delivery status.

• A skipped step: Why this step was skipped or Why this step did not run explains it, such as The run took the other path after an If / else, with the condition that decided it
• A review gate: Gate decision shows Passed, Passed with exclusions, or Blocked, with each check and the products the gate left out. See Who gets a review request.
• A failed step: The error shows in the step's details

When a step fails, Retry above the run's canvas runs the flow again as a new attempt.

1. Navigate to Settings → Flows⁠ and open the flow
2. Click the run under Runs
3. Click Retry
4. Select how to retry. The new attempt opens.

Canceling a run stops it, and its scheduled emails and events aren't sent. Cancel run shows above the canvas while the run is still going.

1. Navigate to Settings → Flows⁠ and open the flow
2. Click the run under Runs
3. Click Cancel run. The status changes to Cancelled.