> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ionq.com/llms.txt
> Use this file to discover all available pages before exploring further.

> Re-queue a job under new settings by cloning it and canceling the original.

# Move job

Move a [job](/user-manual/glossary#job) by [cloning](/api-reference/v0.4/jobs/clone-job) it and canceling the source in a single request. The new job reuses the original [circuit](/user-manual/glossary#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.


## OpenAPI

````yaml https://api.ionq.co/v0.4/api-docs POST /jobs/{UUID}/move
openapi: 3.0.3
info:
  contact:
    email: support@ionq.co
    name: IonQ
    url: https://ionq.com/
  description: |
    *Last updated: June 29, 2026*
    IonQ's API for accessing the IonQ Quantum Cloud platform

    Please subscribe for automated updates when we perform maintenance or
    experience an outage.

    In addition, you may use the [status endpoint](#tag/status) to check the
    current status of our API.

    ## Authentication

    <SecurityDefinitions />
  title: IonQ Cloud Platform API
  version: v0.4
servers:
  - url: https://api.ionq.co/v0.4
security: []
paths:
  /jobs/{UUID}/move:
    post:
      operationId: MoveJob
      parameters:
        - description: The UUID of the job to move.
          in: path
          name: UUID
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CloneJobPayload'
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JobCreationResponse'
        '429':
          description: >-
            Too Many Requests. To get a higher rate limit, please reach out to
            support@ionq.co
        '500':
          description: >-
            A generic server failure, please reach out to support@ionq.co for
            help with this error
        '502':
          description: >-
            Bad Gateway, this can be caused by misbehaving proxies, or by
            service issues. These can be retried, and downtime can be found on
            status.ionq.co
        '503':
          description: >-
            Service Unavailable, this is indicative of service outage, please
            check status.ionq.co
      security:
        - apiKeyAuth: []
components:
  schemas:
    CloneJobPayload:
      $ref: '#/components/schemas/Partial_BaseChildJobCreationPayload_'
    JobCreationResponse:
      properties:
        id:
          type: string
          example: 617a1f8b-59d4-435d-aa33-695433d7155e
        status:
          $ref: '#/components/schemas/JobStatus'
        session_id:
          type: string
          nullable: true
          example: null
      required:
        - id
        - status
        - session_id
      type: object
      additionalProperties: false
    Partial_BaseChildJobCreationPayload_:
      properties:
        parent:
          type: string
        name:
          type: string
        metadata:
          $ref: '#/components/schemas/JobMetadata'
          description: User defined metadata
        shots:
          type: integer
          format: int32
          description: '`shots` is ignored by ideal simulator backend.'
          default: 100
          minimum: 1
          maximum: 1000000
        backend:
          type: string
        session_id:
          type: string
        settings:
          properties:
            error_mitigation:
              properties:
                symmetry_verification:
                  type: boolean
                debiasing:
                  anyOf:
                    - type: boolean
                    - properties:
                        phi_chi_twirling:
                          properties:
                            p2q:
                              type: number
                              format: double
                            t2q:
                              type: number
                              format: double
                            t1q:
                              type: number
                              format: double
                          type: object
                      type: object
              type: object
            compilation:
              properties:
                service_version:
                  type: string
                gate_basis:
                  type: string
                precision:
                  type: string
                opt:
                  type: number
                  format: double
              type: object
          type: object
        dry_run:
          type: boolean
        noise:
          $ref: '#/components/schemas/Noise'
      type: object
      description: Make all properties in T optional
    JobStatus:
      type: string
      enum:
        - submitted
        - ready
        - started
        - canceled
        - failed
        - completed
    JobMetadata:
      properties: {}
      type: object
      additionalProperties:
        type: string
    Noise:
      properties:
        model:
          $ref: '#/components/schemas/NoiseModel'
        seed:
          type: integer
          format: int32
      required:
        - model
      type: object
      additionalProperties: false
    NoiseModel:
      type: string
      enum:
        - ideal
        - harmony
        - harmony-1
        - harmony-2
        - aria-1
        - aria-2
        - forte-1
        - forte-enterprise-1
  securitySchemes:
    apiKeyAuth:
      description: >-
        API keys are associated with a user and can be created on the [IonQ
        Quantum Cloud](https://cloud.ionq.com) application. To authenticate,
        prefix your API Key with `apiKey ` and place it in the `Authorization`
        request header. Ex: `Authorization: apiKey your-api-key`
      in: header
      name: Authorization
      type: apiKey

````