Skip to main content
Move a job by cloning it and canceling the source in a single request. The new job reuses the original circuit and workload, and any fields you provide in the request body — such as name, shots, backend, settings, or metadata — override the inherited values. The cloned job records the source job’s id under metadata.original_job_id. Use this to re-target or re-configure a queued job without leaving the original consuming a queue position. If the source job cannot be canceled — for example because it has already completed — the request fails with a 409 Conflict and no new job is created.