When to use
How a Path Is Built
An execution path is the ordered sequence of spans in one trace. Each span is one step, in order of span start time. Two traces that calledsearch_orders, then get_refund_policy, then the LLM, share one execution path, even if their inputs differ.
How it works
Flows names each step by the action Polaris annotates the span with.
Repeated consecutive calls stay separate steps. The Fold Label adjustment turns consecutive spans with one label into one step. When two runs call the same tools with different arguments, Polaris labels or custom eval scores may split them into separate paths.
Reading the Sankey
Flows draws every execution path in one Sankey, with the number of traces that took each path.Agent Flow From an AI Assistant
The Kubit MCP server builds an Agent flow report when you ask for span labels, tool calls and model calls drawn over whole traces. Report types lists it with the other report types.Example Prompts
“Show the agent flow across our traces over the last 14 days”
“Show me the top 10 execution paths for the support agent in the last 7 days”