# Run records

> What Qsolve stores for every run, how to browse your run history, and how to read the evidence on a run page: receipt, circuits, events and credit movements.

Source: https://qsolve.omlabs.co/docs/use/run-records
Updated: 2026-11-12

Every run leaves a record on your account: what you submitted, what came back, what it cost and the evidence of how it was produced. Browse them on **My runs** and open any one for the full detail. The record is how you audit a result later.

## Run history

**My runs** lists your account's runs, newest first, up to 100 at a time. Each row shows the workflow, a short run ID, a status pill, the result against the baseline ("Matched classical", "x% better" or "x% off"), the target, run time, credits and start time. The page refreshes every few seconds while anything is in progress.

The filter offers **All**, **In progress**, **Done** and **Failed** (which includes stopped runs). A summary line above it gives the number of runs, credits spent and how many are in progress. Everyone in the same account sees the same runs.

## What is stored for each run

Each record holds your submission (input, settings, target, device, seed, spend limit), status and timing, the workflow's estimate and your quote, the result (answer, every method's objective, comparison with the baseline, accuracy, fidelity and circuit figures), cost, the progress log, the circuits sent, the receipt and, if the run failed, the error message with the tail of the workflow's error output.

**Report** on the run page downloads the run and its events as a JSON file.

## The receipt

The **Receipt** card in the side column records exactly what produced the result.

| Field | Meaning |
|---|---|
| Workflow | The workflow name and version |
| Code | The commit of the workflow's repository that ran. Select it to copy |
| SDK | The version of the Qsolve SDK that executed the workflow |
| Input hash | A fingerprint of the input |
| Result hash | A fingerprint of the result |
| Run ID | The run's identifier |

The full provenance also records the target and device, usage (shots, circuits, quantum seconds), the hardware queue wait, and on hardware a snapshot of the device's calibration. It also holds an integrity check: the shots the workflow's result reports against the shots Qsolve metered. If they disagree, the run is stopped.

A **Benchmark run** badge marks the platform's own benchmark runs. Every signed-in user can read these, because their receipts are the evidence behind a workflow's track record. Your own runs are visible only to your account.

## Evidence for the quantum part

### Circuits

The **Circuits** card lists every distinct circuit the run sent:

| Column | Meaning |
|---|---|
| # | Order in which the circuit was first sent |
| Qubits, Depth, Two-qubit | Size of the circuit as written |
| On the chip | On hardware, the two-qubit gate count after the circuit was rewritten for the chip, and which physical qubits it used |
| Sent × shots | How many times it was sent, and with how many shots each time |

Select a row to draw it. For hardware runs a switch shows **As written** or **As run on the chip**; the chip version is usually longer because the circuit was rewritten (transpiled) into the processor's gates and mapped onto its physical qubits.

Qsolve records circuits as they are sent, so this is the circuit that actually reached the machine, not the workflow's description of it. Up to 2,000 distinct circuits are summarised per run, and the full gate list is kept for only the first eight; the rest show "summary only".

### Solver details

**How the solver got there** shows the settings and numbers the solver reported, and **Everything the solver reported** expands to the raw JSON. These are the workflow's own statements, unlike the measured figures elsewhere on the page.

## Retention

Progress events are deleted after 30 days. Ninety days after a run finishes, its input, solver settings and result are cleared, while status, cost, timings and receipt remain. A cleared run cannot be used to rerun the same input. See [Data and privacy](/docs/use/data-and-privacy).