Tracking Workflows with Run History

The Run History feature provides a comprehensive overview of all flow runs at the space level, offering detailed records with filtering and search capabilities. This tool allows you to monitor every step of any flow without requiring additional setup. You can access it by clicking on Spaces, selecting a specific space, and navigating to the Runs tab.

Filter Section

The Run History offers several filters that can help refine the list of runs displayed in the table:

• Filter by Keyword: Allows filtering runs by a specific term.

• Filter by App: Allows filtering by one or more apps within the current space.

• Filter by Node type: Provides the option to filter by either Primary Nodes (default) or All Nodes.

  • Primary Nodes Displays the most important nodes involved in a run, including all qibb nodes and key standard nodes. This filter helps focus on the overall process, hiding technical or debugging details.

  • All Nodes Displays all nodes involved in a run, useful for debugging each step of the flow in detail.

• Time Range: Allows filtering runs based on a specified time range, such as "Last 24 hours."

Optimizing Your Search with Filters
Using filters, such as App and Time Range, can improve the performance of your search results by reducing the dataset, allowing for faster operations.

Additional Options

• Polling interval: Lets you set an automatic polling interval (in seconds) to refresh the Runs table and fetch the latest records. The default is "No polling."

• Refresh button: Allows you to manually refresh the Runs table to display the latest records.

Run History Table Columns

The Run History table includes the following columns:

• Timestamp: Displays the date and time of the run.

• Run: Shows the unique identifier (ID) for the run.

• Node: Lists the node involved after the flow is executed.

• Group: Displays the node’s group if applicable.

• Flow Tab: Shows the flow tab’s ID and name.

• App: Displays the app's ID and name associated with the flow.

Example of Filtering Runs

Below is an example of the Run History table after filtering by a specific keyword and app.

Expandable Run Entries

After a flow is executed, its associated nodes are grouped under an expandable row in the table. You can expand these entries by clicking the arrow icon located on the right side of each row.

• Message content: If a node generates a message object (JSON data processed by each node during a run), an arrow icon will appear to allow you to view the message content.