Last updated: March 2026 Category: Flows
Overview
The Flow History page shows you a detailed log of every flow execution — who entered, what actions were taken, and the outcome. The Scheduled Queue shows upcoming scheduled flow runs. Together, these tools give you full visibility into your automation activity, both past and future.
Prerequisites
At least one active flow with executions
Access to the BeyondCart dashboard
Step-by-Step Guide
Accessing Flow History
Navigate to Flows in the left menu.
Click on a flow to open it.
Click the "History" tab at the top of the editor.
[Screenshot: Flow history tab showing a list of execution entries with timestamps and statuses]
Understanding the Execution Log
Each entry in the history log represents one user's journey through the flow. The log shows:
User — The name and email of the user who entered the flow.
Trigger Time — When the user entered the flow (the moment the trigger fired).
Current Node — Where the user currently is in the flow (if still in progress).
Status — The execution status:
In Progress — The user is still moving through the flow (likely waiting on a delay).
Completed — The user reached the end of the flow.
Converted — The user triggered a Goal event and was recorded as a conversion.
Exited — The user hit an Exit node or was removed from the flow.
Failed — An error occurred during execution (e.g., webhook failure after all retries).
Completed At — When the execution finished (if applicable).
Viewing Execution Details
Click on any execution entry to see the full step-by-step timeline:
Each node the user passed through is listed in order.
For each node, you see:
The node name and type.
The timestamp when the user reached that node.
The outcome (e.g., "Push notification sent," "Condition: took IF branch," "Delay: waited 1 hour").
If a node failed, the error details are displayed.
[Screenshot: Execution detail view showing a timeline of nodes with timestamps and outcomes]
Filtering the History
Use the filters at the top of the history page to narrow results:
Status — Filter by In Progress, Completed, Converted, Exited, or Failed.
Date Range — Show executions from a specific time period.
User Search — Search by user name or email to find a specific person's execution.
Accessing the Scheduled Queue
For flows with a Scheduled trigger, you can view upcoming runs:
Open the flow with a Scheduled trigger.
Click the "Scheduled" tab at the top of the editor.
The queue shows:
Next Run — The date and time of the next scheduled execution.
Frequency — How often the flow runs (daily, weekly, or custom).
Target Segment — The segment that will be evaluated at run time (if configured).
Estimated Users — An approximate count of users who currently match the criteria.
[Screenshot: Scheduled queue showing next run time, frequency, and estimated user count]
Managing Scheduled Runs
From the Scheduled tab, you can:
Skip Next Run — Cancel the next scheduled execution without pausing the entire flow.
Run Now — Trigger an immediate execution outside the normal schedule.
Edit Schedule — Change the frequency or timing without entering the full flow editor.
Key Concepts
History is per-flow. Each flow maintains its own execution history. There is no global history page across all flows.
Execution details are retained for 90 days. After 90 days, individual execution timelines are archived. Summary statistics remain available indefinitely.
The Scheduled tab only appears for flows with a Scheduled trigger. Event-based and Manual flows do not have a scheduled queue.
Tips and Best Practices
Use the history page for debugging. If a user reports they did not receive a notification, search for their execution and check each node's outcome to find where the issue occurred.
Filter by "Failed" regularly. Failed executions may indicate webhook endpoint issues, expired push tokens, or other problems that need attention.
Monitor "In Progress" counts. A large number of users stuck "In Progress" might mean a delay node is too long or a condition is blocking progression.
Use "Skip Next Run" for holidays. If your scheduled flow sends promotions you do not want going out on a holiday, skip the run instead of pausing the entire flow.
Use "Run Now" for time-sensitive campaigns. If you need to send a scheduled flow outside its normal time, run it manually without changing the schedule.
FAQ
Q: Can I re-run a failed execution? A: There is no automatic re-run feature for individual executions. If a failure was caused by a temporary issue (e.g., a webhook endpoint was down), the user would need to re-enter the flow through the trigger.
Q: How long is execution history kept? A: Detailed execution timelines are available for 90 days. After that, they are archived. Aggregate statistics on the Statistics tab are retained indefinitely.
Q: Can I export the execution history? A: Yes. Click the "Export" button on the History tab to download the execution log as a CSV file for the selected date range and filters.
Q: What happens if a scheduled run has zero matching users? A: The run executes but enrolls zero users. It appears in the history as a completed run with no executions.
Related Articles