Run evidence
A background Run detail page shows its source case or plan, trigger, status, timestamps, duration, and individual case outcomes. Plan Runs also show result counts and duration summaries.
Review in order
- Check whether the Run actually executed cases and which cases failed.
- Read the failed reason, including a step number when reported.
- Inspect the case execution and linked Issue when available.
- Open its recording and compare expected behavior with the observed UI.
- Decide whether to update instructions, fix test data, investigate the environment, or track a product issue.
The stored failed reason and recording are the primary execution evidence. A recording can show the screen at failure; do not assume there is a separate screenshot attachment or a stored summary for every step.
Recording availability
The Run result is saved before video processing finishes. Processing means the recording job is pending or running; Completed means playback is ready; Failed means video processing failed. A completed test result can still have an unavailable recording. Refresh the view to check the latest state.
Recordings include the captured browser session and tracked cursor/clicks. Playback requires workspace access and uses a short-lived private link. Run history cleanup can remove the Run and recording according to the current plan. Playback also has a 92-day window measured from the recording upload, so a fresh playback link does not extend evidence retention.
Direct Find issues recordings appear on the Issue as reproduction clips when available. The agent's Live View case result is displayed in its card rather than saved as a background Run.