Flow Report - Analyze a Single Agentic Flow in ConvyAI
Overview
The Flow Report page shows the same analysis as the Dashboard, limited to one Agentic Flow. Use it to understand how a single flow behaves: whether it completes, how long it takes, how many tokens it consumes, which outcomes it produces and which nodes fail.
You can open it:
- from the Agentic Flows page, with the Report button of a flow, which opens the report on that flow;
- from the Dashboard, in the Executions by flow card: use the Flow Report action of a flow row to open the page on that flow, or the Flow Report link in the card footer to open the page and choose the flow from there.
The page is available on tenants with the Agentic Orchestrator module enabled, to the roles that access the Dashboard: agenticorchestrator_admin, agenticorchestrator_user and the higher user levels. The Back to Dashboard link returns to the Dashboard.
Select a flow
Use the selector at the top of the page to choose the flow. It lists the flows that have at least one execution, including renamed or deleted flows, and shows their latest name. When you open the page without a flow, the selector reads Select a flow and the cards stay empty until you choose one.
Changing the flow reloads the cards on the new flow. The period does not change. The flow and the period you choose are kept when you refresh the page, and are lost when you close the browser tab.
Active zone
The Active zone shows the In progress and Waiting cards of the selected flow, with the same meaning as in the Dashboard, including the waiting time bands. It refreshes every minute.
Trends zone
The Trends zone analyzes the executions of the selected flow that ended in the selected period.
The period selector works as in the Dashboard: same presets, same default (Last 7 days), same comparison with the previous period, same refresh. See Choose the period. The period is shared with the Dashboard: if you change it here, you find it changed there, and the other way round.
Executions, Completion rate and Duration
These cards show the same figures as in the Dashboard, for the selected flow. See Read the cards for how to read them, and What p50 and p95 mean for the percentiles.
| Card | What it shows | Delta |
|---|---|---|
| Executions | Executions of the flow ended in the period. | Direction and size only. |
| Completion rate | Percentage of executions that completed. | Percentage points. Favorable when it increases. |
| Duration | Median duration (p50) of completed executions, with the p95 below. | On the p50. Favorable when it decreases. |
The split between errors and stops is in the Technical outcome card.
Tokens per execution
Average Input, Output and Thinking tokens per execution of the flow, with delta, p95 and total of the period, as described in the Dashboard. If the flow ran no AI Agent node in the period, the card shows No AI Agent executions in this period.
Executions over time
A stacked bar chart of the executions of the flow ended in each interval, split into Completed, Errors and Stopped. Hover a bar to see the interval and the figures. Click a bar to open Monitoring on the executions of the flow that ended in that interval, or click a segment to also filter on the corresponding outcome.
Technical outcome
A pie chart of how the executions of the flow ended: Completed, Errors or Stopped. The legend and the tooltip show, for each slice, the number of executions and the percentage of the total. A stop is a voluntary interruption and does not count as an error.
If no execution ended in the period, the card shows No executions ended in this period. Click a slice or its legend entry to open Monitoring on the executions of the flow with that outcome in the selected period.
Results
Shows what the flow declared through its Result nodes, that is how your process ended according to the values you defined. Three numbers appear at the top:
| Number | Meaning |
|---|---|
| Executions | Executions of the flow ended in the period. |
| Outcomes emitted | Total of the outcomes emitted by Result nodes in the period. |
| Ended without outcome | Executions that ended without emitting any outcome. |
An execution can emit more than one outcome, even the same value several times, so Outcomes emitted can be greater than Executions. The three numbers are not meant to be added up.
Below the numbers, a bar list shows the values emitted, most frequent first, with the number of outcomes and the percentage over Outcomes emitted. Each row also shows the value of the same outcome in the previous period, with no arrow and no delta: the platform does not know the business meaning of your values, so it does not tell you whether a change is good or bad. Values appear exactly as you wrote them in the Result node.
The list shows the 5 most frequent values. All the others are grouped in Other values. All ended executions count, whatever their final state, because an outcome emitted before an error or a stop is still valid. Rows are not clickable.
Errors by node
Shows where the errors of the flow concentrate. Three cards show the three nodes with the most errors in the period, most errors first. Each card shows:
- the name and type of the node, for example HTTP Request;
- the errors of the node in the period and in the previous period;
- the delta, as a percentage change: favorable when errors decrease, unfavorable when they increase;
- two sparklines with the errors over time: solid for the current period, dashed for the previous one.
Each sparkline has its own scale: read it to see the trend of the node, and compare the nodes using the number of errors.
Below the cards, Other nodes sums up the errors of the remaining nodes, Not attributed the errors with no associated node (shown only when greater than zero), and the total of the errors of the period is reported.
Related topics
- Dashboard - tenant-wide view of active executions and trends
- Monitoring - list, filter and inspect individual executions
- Result node - define the process outcome of an execution