Loading docs
Understand run feedback, simulator and hardware execution paths, queue context, and safe retry behavior.
Running a workflow should be explicit. The user should know which workflow was submitted, which route was selected, and where evidence will appear.
Treat simulator and hardware runs differently in notes. Simulator runs are useful for fast iteration; hardware runs should include provider and queue context.
Section 01
Confirm the canvas, generated code, provider selection, and analysis state. If a user cannot explain what will run, pause and inspect the workflow first.
For team workflows, record the success criteria before execution. That makes the result easier to interpret.
Section 02
Check immediate feedback and then return to run history. The run record should carry status, artifacts, and evidence context.
If a run fails, keep the failed record. It is often useful for debugging provider readiness, circuit constraints, and retry decisions.