Skip to main content
A job is created each time you run something: haiqu.run(...), a transpilation, a data-loading or a hybrid program. All Jobs lists every job across all your experiments.

​
Statuses

A job moves through these statuses. While any job is in progress, the list refreshes on its own every 15 seconds.

​
Metrics in the table

QPU Quality is empty for circuits with 20 or more qubits: it needs a classical simulation, which is not feasible at that size. An empty value is not an error. See Job Performance Metrics.

​
Find a job

  • Search by name, and filter by Type, Status or Backend. Haiqu OS groups jobs that don’t target a QPU or simulator, such as transpilation or variational jobs.
  • Click a Type or Backend badge to filter by it. Hover over a job ID to copy it; click a name or description to edit it.

​
Results and actions

The icons at the end of each row:
  • View input circuit(s) / View output circuit(s): the experiment’s circuits, filtered to this job.
  • View bitstrings: Job Results, the measured bitstrings and their probabilities, most likely first.
  • View observables: for jobs that measure observables, Job Results shows the returned values as JSON.
  • Details: the job details page (Run jobs).
  • … menu: View Logs, Cancel (jobs in progress), Restart (jobs in Error or Cancelled), Delete.
Both results views have Export to JSON.

​
What Restart does

Restart runs the same job again: it keeps its ID and its original circuits, parameters and device, and goes back to Submitted. It is charged like a new run. To change anything — the device, shots or options — submit a new job from the SDK instead.

​
Job details

The job details page shows the job’s status, type, backend and experiment, followed by three sections:
  • Quantum Flow Graph: each step of the job, from the input circuit through transpilation and error mitigation to the device. Hover over a step to see what it does.
  • Circuits: the circuits this job ran.
  • Results: Probability vs Bitstring: a chart of the 10 most likely outcomes. Use the download icon to export all results as JSON.
Results are also available in the SDK. See haiqu.run.

​
Troubleshooting

On a real QPU, Running includes waiting in the provider’s queue. Check the device’s Queue and Load (7 days) on Devices; a long queue means a long wait. Cancel the job and run it on a less busy device if you can’t wait.
Open … → View Logs: the last lines show the reason. If it was temporary, such as a provider outage, use Restart. If it was an authentication error (for example, an expired provider token), Restart will fail again because it reuses the job’s original options: submit a new job from the SDK with valid credentials. The same applies when the circuit or options need to change.
View bitstrings appears only for jobs that return measurement counts; jobs that measure observables show View observables instead. An empty QPU Quality for 20 or more qubits is expected (see above).
Check that the SDK is logged in with the API key shown on your Dashboard home, and look under the experiment you initialized with haiqu.init("name"). See also Account & Credits.