Flow Runs and logs
The Runs section in ZBrain Flows provides a consolidated view of your Flow execution history, including status, duration, token usage, and cost. This enables you to monitor resource consumption, troubleshoot failures, and rerun specific executions as needed.
Accessing Flow Runs details
Navigate to the Flows tab from the top menu.
Select Runs from the left-hand sidebar.
The interface will display a list of recent executions for all flows in your workspace.
If you want to see the flow execution details for a particular Flow, select the particular Flow from the Flows tab and click Logs from the left panel.
Runs table overview
The Runs table contains the following key columns:
Flow – Name of the executed Flow.
Status – Execution result, shown with a visual indicator:
Succeeded – Flow completed successfully.
Failed – Flow encountered an error during execution.
Paused – Flow execution was paused manually or by a system trigger.
Started – Date and time when execution began.
Finished – Date and time when execution ended.
Token Used - Per-activity token usage
Cost ($) - Cost per activity
Execution Time – Total time taken to complete the run.
The Filter by Status option allows users to view flows based on their execution status. You can select from different statuses to refine the list of runs, as shown in the image below:
The Filter by Flow Name option allows users to refine the displayed list of runs by selecting one or more flow names. This feature supports multi-select, enabling precise control over which flows are shown in the Runs view. You can select multiple flows and deselect a selected flow name by clicking on it again.
Retrying a Flow Run
ZBrain Builder provides flexible retry options to help you recover from failed or incomplete executions without needing to restart the entire workflow manually. Retry actions are available from the (⋯) on the corresponding row in the table. Click (⋯) and select from the below available options -
Retry on latest version – Executes the flow again with the most recently published version, ensuring all updates and fixes are applied.
Retry from failed step (for failed runs) – Restarts the flow from the point of failure, preserving prior completed steps to save time and resources.
Best practices
Regularly filter and review Failed runs to ensure critical workflows are not blocked.
Use Retry from Failed Step when debugging to avoid unnecessary reprocessing of completed steps.
Monitor Execution Time trends to spot anomalies or performance degradation.
Last updated