Insights is currently in beta. Share your feedback with your Customer Success Manager (CSM) to help us improve.
At-a-Glance metrics are four key performance indicators that provide a quick health check of platform or workflow performance.
Where they appear:
- Summary Dashboard: Platform-wide metrics aggregated across all root jobs
- Workflow Details: Workflow-specific metrics filtered to a single workflow
Each metric displays:
- Current value: The metric for your selected time range
- Percentage change (delta): Comparison to the equivalent previous period
- Trend indicator: Visual arrow showing direction of change
Scope:
- Summary Dashboard: Calculates using root jobs only.
- Workflow Details: Calculates based on the Root Jobs / All Jobs (Root and Child) toggle selection.
Metrics
Jobs Run
The total count of jobs executed during your selected time range.
Interpretation:
- Upward trend (â–²): Platform usage is growing - automation adoption is increasing
- Downward trend (â–¼): Platform usage is declining - may indicate reliability concerns, reduced confidence, or seasonal variation
- Stable trend (—): Mature, consistent usage - may signal opportunity to expand automation
Business value: This metric demonstrates platform adoption and helps identify whether automation is being actively used and growing.
Example scenarios:
| Value | Trend | Example interpretation |
|---|---|---|
| 2,504 jobs | â–² 12% | Good: Platform usage growing, increased automation adoption |
| 1,850 jobs | â–¼ 8% | Investigate: Usage declining, check for issues or seasonal patterns |
| 3,200 jobs | — 0% | Mature usage: Consider expanding automation to new areas |
Completion Rate
The percentage of jobs that completed versus those that were canceled.
Calculation: (Completed jobs / Total jobs) × 100
Where Total jobs = Completed jobs + Canceled jobs
Jobs can reach completion by:
- Completing successfully through their intended path
- Completing through a defined error transition or failure path
Interpretation: A declining completion rate indicates that more jobs are being canceled before reaching completion. This may signal workflow design issues, timeout problems, or infrastructure constraints.
This metric compares completed versus canceled jobs. Jobs in error or running states are not included in this calculation. This metric measures execution completion, not whether jobs accomplished their intended business outcomes.
Example scenarios:
| Value | Trend | Example interpretation |
|---|---|---|
| 100% | — 0% | Excellent: All jobs completing, workflows handling errors properly |
| 95% | â–¼ 3% | Concerning: More being canceled, investigate workflow logic |
| 88% | â–¼ 5% | Critical: Significant number of jobs being canceled, immediate action required |
What to do if completion rate is declining:
- View the Workflow Highlights table to identify which workflows have canceled jobs
- Review workflow logic for proper error handling and completion paths
- Check for jobs stuck in "Running" state that never complete
- Use Job Viewer to examine specific jobs that didn't complete
- Verify all workflow paths (success and error) lead to job completion
Total Runtime
The cumulative execution time of all jobs in your selected time range.
Business value:
- Justifies infrastructure investments when load increases
- Identifies performance degradation requiring optimization
- Validates optimization efforts when runtime decreases with stable usage
- Helps predict resource needs for capacity planning
Example scenarios:
Context is important when interpreting the Total Runtime metric. The following examples interpret the Total Runtime metric within the context of the associated Jobs Run metric.
| Jobs Run | Total Runtime | Example interpretation |
|---|---|---|
| 2,500 jobs (stable) | 42 hours (â–² 25%) | Performance degradation: jobs taking longer to complete, investigate performance |
| 3,000 jobs (â–² 20%) | 50 hours (â–² 22%) | Healthy growth: runtime increasing proportionally with usage |
| 2,500 jobs (stable) | 35 hours (â–¼ 15%) | Success: optimization efforts are working |
| 2,000 (â–¼ 20%) | 32 hours (â–¼ 18%) | Reduced usage: runtime decreasing proportionally with usage, investigate adoption |
What to do if runtime is increasing disproportionately:
- View the Workflow Highlights table to identify workflows with increasing median runtimes
- Review system resource utilization and external integration performance
- Consider infrastructure capacity or optimization needs
Time Saved
The cumulative manual effort avoided through automation, not the difference between manual time and automation execution time. The value is in avoiding manual work, regardless of automation speed.
Calculation: Σ(Pre-automation Time for each job)
Interpretation:
- High time saved with green â–²: Excellent ROI and growing automation value
- Low or empty time saved: Pre-automation time not configured for workflows
- Time saved with red â–¼: Fewer jobs running or workflows with high pre-automation time executing less frequently
Business value:
- Directly quantifies ROI in hours saved
- Essential for executive reporting and renewal conversations
- Justifies automation investments with concrete metrics
- Demonstrates value to stakeholders in understandable terms
Example scenarios:
| Value | Trend | Example interpretation |
|---|---|---|
| 1,250 | â–² 18% | Excellent: Growing automation value and ROI |
-- (empty) |
N/A | Action needed: Configure pre-automation time in Studio |
| 890 hours | â–¼ 10% | Review needed: Are fewer jobs running or different workflows being included in metric calculation? |
If time saved is empty or low:
- View the Workflow Highlights table and filter by Missing Pre-Automation Time
- Identify workflows without pre-automation time configured
- Click Set Time to navigate to Studio and configure values
See Configure pre-automation time for setup instructions.
Use metrics together
The four at-a-glance metrics are most powerful when analyzed together:
Healthy growth pattern
- Jobs Run: â–² 15%
- Completion Rate: 100% (stable)
- Total Runtime: â–² 16%
- Time Saved: â–² 15%
Example interpretation: Platform growing, all jobs completing, delivering value
Workflow reliability issue pattern
- Jobs Run: Stable
- Completion Rate: 95% (â–¼ 5%)
- Total Runtime: Stable
- Time Saved: Stable
Example interpretation: Some jobs failing to complete - workflow logic or error handling issues need attention
Adoption concern pattern
- Jobs Run: â–¼ 20%
- Completion Rate: 100% (stable)
- Total Runtime: â–¼ 20%
- Time Saved: â–¼ 20%
Example interpretation: Platform usage declining - investigate confidence issues or seasonal factors