Changelog

Changing a measurement selection quickly — select, deselect, select again — could end up in the wrong state a few seconds later, showing no results until the page was reloaded.

• Fixed rapid filter and selection changes occasionally reverting to an earlier state (a race in the URL state library, fixed upstream and upgraded)
• Fixed measurement names containing a comma breaking multi-selection entirely
• Selecting a measurement now applies in a single step instead of two, removing a flicker

Exporting from Phase Pareto or Measurement Control only covered the rows already loaded on screen — filter to 295 phase executions, export, get 50.

• Added "Export all matching" to both export menus — the file now contains every row matching your filters, with a clear warning if the export is very large
• Added selection chips to the Measurement Control search bar, so the selected measurement shows up there and can be cleared in one click
• Fixed removing a filter chip doing nothing, and filters occasionally conflicting when changed quickly from different places
• Made Measurement Control load faster on first visit

Deploying with the CLI created a deployment you could open by link, but the Deployments page still claimed no repository was connected and listed nothing.

• Fixed the Deployments page hiding CLI deployments on procedures with no linked Git repository.
• Fixed the same blank state on the organization-wide Deployments page.
• Updated the empty state to mention tofupilot deploy alongside connecting a repository.

Filters that silently matched nothing were hard to notice and easy to reintroduce. Alongside the fix, we tightened how filters are built and tested.

• Rebuilt the filter search syntax so quoted values survive intact, covered by an exhaustive test suite
• Made a misconfigured filter fail immediately instead of quietly rendering nothing
• Fixed long filter names pushing their counts out of column, and shortened them with the full name on hover

Filtering on a name that contains a space — a phase called "Contact Voltage Drop", a batch called "Lot 2024 rev B" — matched only the first word and returned nothing.

• Fixed filters on values containing spaces or commas, everywhere filters are used
• Added export to the Phase Pareto and Measurement Control toolbars, matching runs and units
• Added the search bar to Measurement Control

Offboarding a team member is now a single action with nothing left to clean up by hand.

• Removing a member now automatically deactivates their organization API keys and MCP connections in one step
• Improved the remove and re-invite flow so returning members get a fresh start while their test history stays intact
• Updated the member management docs to walk through the new offboarding flow

Phase Pareto and Measurement Control are the two analytics tables that could not be exported, so getting their data into a spreadsheet meant copying rows by hand.

• Added CSV and JSON export to the phase and measurement lists, available from the selection bar once rows are selected.
• Added a copy-to-clipboard option so selected rows can be pasted straight into a spreadsheet.
• Kept numeric, boolean and text measurement values in separate columns so numbers stay sortable in the exported file.

Managing who has access to your organization is now simpler and safer.

• Replaced account suspension with a clear "Remove from organization" action that revokes access without touching the person's account elsewhere
• Removed members keep their history: runs and records they created stay fully visible for traceability
• Restoring access is now a simple re-invite

A yield alert could close itself while the line was still failing. The drop that raised it slowly became part of the baseline it was being compared against, so a single quality incident produced a string of alerts opening and closing on their own — one incident on a production line generated nine.

• Fixed yield alerts closing on the very failures that raised them, so one incident now stays one alert until someone resolves it
• Locked each alert to the baseline measured when it was raised, so the bar to close it no longer drifts while the incident is still open
• Applied the same rule to custom yield rules, which recalculated their reference window on every check

Every alert can now launch an AI root-cause investigation on demand — testing hypotheses against production data and reporting what actually changed.

• Added a root-cause investigation to every alert, started with one click: it builds a live hypothesis tree scoped to the incident window, tests each lead against baseline data, and shows the supporting evidence as charts.
• Added a written conclusion that highlights the most likely cause(s), with recommended next steps split into immediate fixes and longer-term improvements grounded in the findings.
• Added drift attribution that pinpoints whether a measurement shifted in level, spread, or ranking, plus incident-vs-baseline checks for outcome shifts and retest churn.
• Added stop and re-run controls for investigations, with results visible to everyone in the organization.