Control what a run keeps

Choose whether runs keep status and timing only or masked content too, and how long.

In short

"Run storage" decides what each run of a project keeps and for how long. It keeps status and timing only, or also the request and response headers and bodies, with secrets masked, so you can inspect a run later.

Before you start

Who: changing Run storage is a project setting and needs Manage. Opening captured content is recorded in the project's audit log.
Plan: every plan.
Defaults: see the "Run storage" panel; a choice applies to new runs only.

Steps

Open "Project settings", choose "Runs" and find "Run storage".
Choose "Status and timing only" or "Keep masked content".
Set how many days runs are kept.

Result: new runs keep what you chose; a shield icon on a run opens its captured content.

Good to know

"Export" saves a run's captured content as a file; delete removes the content, not the run.
The project's audit log records every view, export and delete; people who manage permissions open it from the board's menu.
Retention cleanup removes captured content after the number of days you chose.

Production responses are real Capturing content for a project that has a Production environment stores real production responses. Turn it on only where that is allowed.

If something goes wrong

A run has no content to compare: the project keeps status and timing only.