---
title: "Lists the execution status of the Job Preparation and Job Release task for the specified job across the compute nodes where the job has run."
method: GET
path: "/jobs/{jobId}/jobpreparationandreleasetaskstatus"
tags: ["Jobs"]
---

# Lists the execution status of the Job Preparation and Job Release task for the specified job across the compute nodes where the job has run.

`GET /jobs/{jobId}/jobpreparationandreleasetaskstatus`

This API returns the Job Preparation and Job Release task status on all compute nodes that have run the Job Preparation or Job Release task. This includes nodes which have since been removed from the pool. If this API is invoked on a job which has no Job Preparation or Job Release task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

## Path parameters

- `jobId` string, required

## Query parameters

- `$filter` string
- `$select` string
- `maxresults` integer
- `timeout` integer
- `api-version` string, required

## Headers

- `client-request-id` string, uuid
- `return-client-request-id` boolean
- `ocp-date` string, date-time-rfc1123

## Response `200`

A response containing a list of Job Preparation and Job Release task statuses.

- CloudJobListPreparationAndReleaseTaskStatusResult
  - `odata.nextLink` string
  - `value` JobPreparationAndReleaseTaskExecutionInformation[]
    - `jobPreparationTaskExecutionInfo` JobPreparationTaskExecutionInformation
      - `containerInfo` TaskContainerExecutionInformation
        - `containerId` string
        - `error` string — This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by "docker inspect".
        - `state` string — This is the state of the container according to the Docker service. It is equivalent to the status field returned by "docker inspect".
      - `endTime` string, date-time — This property is set only if the task is in the Completed state.
      - `exitCode` integer — This parameter is returned only if the task is in the completed state. The exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. Note that the exit code may also be generated by the compute node operating system, such as when a process is forcibly terminated.
      - `failureInfo` TaskFailureInformation
        - `category` 'usererror' | 'servererror', required
        - `code` string
        - `details` NameValuePair[]
          - `name` string
          - `value` string
        - `message` string
      - `lastRetryTime` string, date-time — This property is set only if the task was retried (i.e. retryCount is nonzero). If present, this is typically the same as startTime, but may be different if the task has been restarted for reasons other than retry; for example, if the compute node was rebooted during a retry, then the startTime is updated but the lastRetryTime is not.
      - `result` 'success' | 'failure'
      - `retryCount` integer, required — Task application failures (non-zero exit code) are retried, pre-processing errors (the task could not be run) and file upload errors are not retried. The Batch service will retry the task up to the limit specified by the constraints.
      - `startTime` string, date-time, required — If the task has been restarted or retried, this is the most recent time at which the task started running.
      - `state` 'running' | 'completed', required
      - `taskRootDirectory` string
      - `taskRootDirectoryUrl` string
    - `jobReleaseTaskExecutionInfo` JobReleaseTaskExecutionInformation
      - `containerInfo` TaskContainerExecutionInformation
        - `containerId` string
        - `error` string — This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by "docker inspect".
        - `state` string — This is the state of the container according to the Docker service. It is equivalent to the status field returned by "docker inspect".
      - `endTime` string, date-time — This property is set only if the task is in the Completed state.
      - `exitCode` integer — This parameter is returned only if the task is in the completed state. The exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. Note that the exit code may also be generated by the compute node operating system, such as when a process is forcibly terminated.
      - `failureInfo` TaskFailureInformation
        - `category` 'usererror' | 'servererror', required
        - `code` string
        - `details` NameValuePair[]
          - `name` string
          - `value` string
        - `message` string
      - `result` 'success' | 'failure'
      - `startTime` string, date-time, required — If the task has been restarted or retried, this is the most recent time at which the task started running.
      - `state` 'running' | 'completed', required
      - `taskRootDirectory` string
      - `taskRootDirectoryUrl` string
    - `nodeId` string
    - `nodeUrl` string
    - `poolId` string

## Other responses

- `default` — The error from the Batch service. If this API is invoked on a job which has no Job Preparation or Job Release task, the Batch service returns HTTP status code 409.

---

[API](https://skmtc.net/windows/apis/batch-batchservice.md) · [All operations](https://skmtc.net/windows/apis/batch-batchservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/windows/batch-batchservice/versions/9ab62bb93c5f/schema)