Phase Pareto
Last updated on June 16, 2026
Phase pareto works at the Phase level. It ranks phases by how often they fail, how often they retry, and how long they take, so you can target the weakest step in your test instead of guessing.
Failures
The Failures view lists every phase that has failed in the selected range, sorted by failure count. Phases that have never failed are hidden.
Click a phase to surface the Measurements that triggered the failures, then jump into Measurement Control to look at the Cpk and control charts for those measurements.
Retries
The Retries view ranks phases by retry attempts, surfacing the steps that churn through repeated tries before passing. Retries are counted across every attempt, not just the final one.
Duration
The Duration view lists phases by average wall-clock duration, longest first.
Click a phase to see duration over time. Use it to spot regressions after a Deployment or to find the bottleneck in a long procedure.
Filters
Phase pareto shares the analytics filter bar, kept in sync between the sidebar and the command bar.
- Date range: pick a preset or a custom window. The window scopes to when each phase ran.
- Phase outcome: filter by phase result, distinct from the parent run outcome.
- Sample class: production, golden, or failing units.
- Batch, procedure version, part name, and revision: slice the data the same way you would on the yield view.
How is this guide?
Measurement Control
Learn how to detect drift, instability, and bottlenecks at the phase level with TofuPilot Measurement Control: Cpk, control charts, and rankings.
InsightsPreview
Learn how to author saved visualizations of run, unit, and measurement data with TofuPilot Insights, the building blocks of every analytics report.