Definition
The trace timeline places notable run events in time, including navigation, console warnings or errors, and failed or slow network requests.
What it is for
It connects a visible failure to what the browser and network were doing at that moment.
How it works
- Rima places notable events on a time axis: navigations, console warnings and errors, and failed or slow network requests.
- Click a marker to inspect the event; align it with the video and screenshots to see what the page looked like at that moment.
- In multi-test runs you can filter the timeline to one test.
Example
A marker at 12.4 seconds shows a slow API request immediately before the page validation timed out.
Common use cases
- Correlate failures with network activity.
- Find redirects.
- Locate console warnings.
- Understand where a run spent time.
Where to find it
Open a run trace and select the Timeline tab. Filter to one test when a run contains several.
Limitations, requirements, and permissions
- Only events captured during the run appear; the timeline is read-only.
- Requires the run trace to be available.
Related features and guides
Ready to try it yourself?
Create your free account, record your first flow, add a validation, and let Rima run it on a schedule for you.
Start free trial