Skip to main content
Signals highlights what broke after working and what looks flaky over the last 90 days of recorded runs.

​
Review signals

  1. Open Signals from the sidebar in the workspace you want to investigate.
  2. Filter by environment, signal type, or time range. Search by test or spec file to narrow the list.
  3. Review Flaky, Regression, and New failure signals alongside the test’s recorded outcomes.
  4. Use Refresh to request updated results after runs finish.
Signals depends on reported run history. An empty list can mean no matching signals were found or there is not enough recorded history; clear filters and check Past Runs. Use flaky-test checks to repeat the same Patrol and inspect inconsistent outcomes directly. A signal is a reason to investigate, rather than proof of the cause of a failure.