Find a run
Narrow down the list with the filters at the top:- Status: All, Success, Error, or Timeout
- Search by correlation ID: find one specific run. Callers set the correlation ID with the
X-Correlation-Idheader, see Tag a run with a correlation ID. - The time window and the version filter
An expanded run shows its correlation ID, input, output, and the Replay button.
Replay a run
Click Replay on a run to open its recorded trace on the diagram of the release that ran. You can follow the exact path the run took, step by step. Replay does not run the Blueprint again; it shows what happened at the time. Click Runs above the diagram to return to the list. To share a replay with a colleague, click the link icon next to Replay (Copy link to replay).Create a test case from a run
When a production run shows a case worth keeping, turn it into a test:- Expand the run and click the clipboard icon next to Replay (Create test case from run).
- The dialog is prefilled with a name, the run’s inputs, and its result as the expected outputs. It names the test suite the case is added to. If the Blueprint has no test suite yet, Leapter creates one.
- Adjust the values if needed. Each expected output is either Checked (compared with the actual result when the test runs) or Ignored. Click the pill next to an output to switch.
- Click Add test case.
The dialog is prefilled with the run's inputs and its result as expected outputs.
What to do next
- Test Suites: run the test cases you captured from production
- Logic Usage: see which parts of your logic production reaches
- Web API (OpenAPI): set the correlation ID when you call your project