Definition
Run artifacts are the evidence produced by an execution, including screenshots, traces, videos, logs, and downloadable files.
What it is for
Artifacts preserve what happened so a failure can be reviewed later or shared with someone else.
How it works
- During a run Rima saves screenshots, video, a trace archive, logs, and any generated files alongside the results.
- The run Files page lists each artifact with an icon and an open or view link; CLI runs also keep local copies under
~/.rima/runs/. - Artifacts are linked from the run summary and trace viewer wherever they are relevant.
Example
Download the screenshot from the failed checkout step and the trace archive for a developer investigating the API error.
Common use cases
- Attach evidence to a bug.
- Audit a successful flow.
- Download generated files.
- Keep a local copy of a trace.
Where to find it
Open a run and choose Files, or use artifact links from the run summary and trace.
Limitations, requirements, and permissions
- Raw data files are hidden from direct download and surfaced through dedicated views instead.
- Artifacts require access to the run; what was captured depends on run options (the CLI can disable trace or video).
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