Dashboard Overview
The top of the dashboard shows aggregate metrics across all workflows:
Use the date range picker in the top-right corner to adjust the time window. Defaults to the last 7 days.
Integration Usage
The integration usage chart shows which integrations are used most frequently across all workflow executions. Each bar represents an integration (Slack, GitHub, Jira, Linear, Kestrel RCA, etc.) with the total number of action executions.- Paginated — use the navigation controls to browse through all integrations
- Sorted by usage count (highest first)
- Hover over a bar to see the exact count and percentage of total
Execution Duration by Workflow
A paginated bar chart showing the average execution duration for each workflow. Identifies slow workflows that may need optimization.- Each bar represents one workflow, labeled by name
- Duration is the average end-to-end time from trigger to final step completion
- Color-coded: green for fast (under 30s), yellow for moderate (30s–2min), red for slow (over 2min)
- Paginated for organizations with many workflows
Slowest Steps
A ranked list of the slowest individual steps across all workflows, based on average execution time. Each entry shows:
Use this to identify steps that slow down your workflows — whether it’s a slow external API, a long-running AI analysis, or a blocking approval gate.
Execution History
The execution history table lists every workflow run with filtering and search.Filters
Table Columns
Click any row to open the execution detail view.
Execution Detail View
The detail view shows the full step-by-step breakdown of a single workflow execution. Each step displays:- Status: Success, failed, skipped, or pending
- Duration: How long the step took
- Input: The resolved template variables passed to the step
- Output: The full output returned by the step (API responses, AI analysis results, created resource IDs)
- Error: If the step failed, the error message and details
Step outputs are retained for 30 days. After that, execution metadata (status, duration, timestamps) is kept but outputs are purged.
Debugging Failed Executions
When a workflow fails:- Open the execution detail view
- Find the step with a Failed status badge
- Expand the step to see the error message
- Check the Input section to verify the template variables resolved correctly
- Check the Output section for the raw error response from the integration
- Authentication expired — Reconnect the integration on the Integrations page
- Rate limiting — The external API returned a 429. Increase the cooldown period or reduce workflow frequency
- Invalid template variable — A referenced variable was null or malformed. Check the upstream step’s output
- Approval timeout — An approval gate was not responded to within the configured timeout
Next Steps
- Create Workflows — Build new workflows or optimize existing ones
- Custom Integrations — Add HTTP actions and webhook triggers