Compare two runs of a request

Set two runs side by side to see what changed in the response.

In short

Comparing two runs shows what changed between them: time, size, status, headers, body shape, the checks whose verdict changed and what was sent differently. It is the fastest way to find when and why a request started to fail.

Before you start

Who: anyone who can open the project (View). Bodies are compared only when both runs kept their content, and opening it is recorded.
Plan: every plan.
First: the request needs at least two runs.

Steps

Open a request's history, or "Runs".
Tick two runs, or choose "Compare in full" under "What changed since it last passed".
Read them side by side, earlier first.

Result: every difference is listed - time, size and status, response headers and body shape, checks that changed, and what was sent differently.

Good to know

Bodies are compared only when both runs kept their content, and opening it is recorded in each run's history. Body shape is compared either way.
A request's history lists the same call over time with who ran it, the status, the time and any error. If 29 August shows 1,900 ms and every other day about 180 ms, that is the day to ask about - and the run says who ran it.
On a phone each run in the history is a labelled card. Ticking two runs offers to compare them.

If something goes wrong

The bodies are not compared: one of the runs did not keep its content. Body shape is still compared.