Results, history and analytics

Read an execution (video/screenshots), history, and reliability analytics.

syntheticsexecutionshistoryanalyticsflakiness

Reading results, history and analytics

An execution

Open a run (/synthetic/executions/:executionId) to see step-by-step pass/fail, the performance breakdown (DNS, connect, TLS, TTFB, Web Vitals), and — on failure — the screenshot and video at the point it broke, plus captured requests.

History

The History tab lists past runs; filter by test/agent/result to find a flaky window or confirm a fix held.

Analytics

Analytics turns runs into reliability signal: flakiness rate, duration baselines, and trends — so you catch a slow-creep regression, not just the latest red.

Cookbook: a journey "sometimes" fails

  1. Open History and filter to the failing test.
  2. Open a failed run; watch the video to see exactly where it diverged.
  3. Usually a missing wait or a brittle selector — fix the step, re-run, and confirm in Analytics that flakiness drops.
To also verify the backend the journey hit (trace, DB row, logs), wrap the test in a Workbook.