# 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.

* Apply preset time filters—15 minutes, 30 minutes, 1 hour, 6 hours, 1 day, or 3 days—by clicking ‘Pick a date range’ in the Runs view. The table will instantly refresh to display executions that match the chosen timeframe. * Last 15 Minutes * Last 30 Minutes * Last 1 Hour * Last 6 Hours * Last 1 Day * Last 3 Days * **How to use** * Navigate to **Flows → Runs**. * Click ‘**Pick a date range’** at the top of the Runs view. * Select a preset option from the list. * The Runs table will instantly refresh to display executions that match the chosen timeframe.

* 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. * **Identifier** - A unique value linking parent and child flow executions for easier tracing and debugging. You can pass an identifier when triggering a parent Flow (via Postman or HTTP), which automatically propagates to child Flows, making it easy to trace, debug, and monitor complex executions with full visibility. 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. The Flow run names in the Runs view sync with the latest Flow names, eliminating confusion when flows are renamed.

### **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 - 1. **Retry on latest version** – Executes the flow again with the most recently published version, ensuring all updates and fixes are applied. 2. **Retry from failed step** *(*for failed runs) – Restarts the flow from the point of failure, preserving prior completed steps to save time and resources.

#### Stopping a Flow run You can manually stop a running Flow from the Runs page in the Flows section.. This action immediately initiates a controlled shutdown process for the selected flow. You can run a Flow in the following ways: 1. Using Postman 2. By triggering a Flow through an Agent or Agent Crew To stop a Flow: **Go to the Flows module** Log in to ZBrain Builder and open the **Flows** section from the main navigation. **Open All Flows** 1. By triggering a Flow through an Agent or Agent Crew 2. Select **All Flows** to view the complete list of available and active flows. **Find the running flow** Once the Flow is running, you can see the Flow status as Running in the **Runs** page**.** A **Cancel** button appears for the Flow run. Click the 'Cancel' button to stop the Flow.

Once the Flow is stopped, the system starts a controlled stop process. During this stage: * Running tasks are instructed to stop safely * No new tasks are started for that flow * The system prevents abrupt termination that could create inconsistent states In the Recent Run Status, you can check that the Run has been canceled.

### Opening Flow Run details in a new tab You can open Flow Run details in a separate browser tab, giving you more flexibility when reviewing or comparing multiple runs. #### How to use 1. Go to **Flows → Runs**. 2. Locate the Flow Run you want to inspect. 3. To open the Run details in a new tab, use one of the standard browser actions: * **Ctrl + Click** (Windows/Linux) or **Cmd + Click** (Mac) * **Right-click** on the run and select ‘**Open link in new tab’** 4. The Run details will open in a separate browser tab, while your Runs list remains available in the original tab. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-runs-and-logs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.