Job Result Statuses List

2038

Canceled - Blackout

0

This status means the patch deployment job is canceled on the asset due to blackout window.

Y

Y

Y

2036

Completed

0

This status means the patch deployment job is completed on the asset.

Y

Y

Y

2031

Downloaded

1

This status means patch file is successfully downloaded on the asset.

Y

N

N

2031

Downloading - Failed

2

This status means patch failed to download on the asset.

Y

N

N

2057

Execution Blocked

1

This status means that the job execution couldn’t start at the scheduled time because another job is currently running. Refer to the following format and example to understand how the message is shown on the UI:

The job execution couldn’t start at the scheduled time because another job <current running job name> is currently running. This job will run if the currently running job gets completed in a permissible patching window. Else, it will time out.

Example: The job execution of 'Job 2' couldn’t start at the scheduled time because 'Job 1'  is currently running. Job 2 will run if the currently running Job 1 gets completed in a permissible patching window. Else, it will time out.

Y

N

N

2046

Job Failed

0

This means the agent encounters an error while executing the job.

Y

Y

Y

2055

Job Received

1

This status means that the job is downloaded by the agent and it will execute at the scheduled time.

Y

Y

Y

2045

Job Resumed

0

This means the asset is restarted and agent has resumed the job.

Y

Y

Y

2044

Job Started

0

This status means the agent has started the job.

Y

Y

Y

2059

No Patch Available

1

This status means that the job does not include any patch and any pre-post action.

Y

N

N

2053

Not Applicable

1

This status means that the patch is not applicable for a particular asset operating system version.

2039

Not Licensed

2

This status means job manifest can not be sent as the asset does not have Patch Management license.

Y

N

N

2033

Patching

0

This status means the patch job is running on the asset.

Y

N

N

2032

Pending

0

This status means the patch job is pending for execution on the asset. The messages are shown based on different scenarios:

The following message is shown before the job manifest is sent to the agent:

- The job preparation is in progress and will be available for the agent to download as per the schedule.

The following message is shown when the job manifest is generated and made available for the agent:

- The job is available for the agent to download. The agent will download the job when it checks-in.

Y

Y

Y

2034

Pending Reboot

0

This status means if a windows asset is waiting for reboot of a job, then it will not pick any other job for processing. Other jobs will be added to the queue.

This status means if a Linux asset is waiting for reboot of a job, it will still pick other jobs for processing.

Y

Y

Y

2058

Reboot Deferred

0

This status means that the end-user deferred a reboot request. Refer to the following format and example to understand how the message is shown on the UI:

The end-user deferred an asset reboot request. Deferral count: (<Total used reboot deferral> of <Total available reboot deferral>)

Example: The end-user deferred an asset reboot request. Deferral count: (1 of 5)

Y

Y

N

2035

Rebooted

0

This status means asset is restarted after patch installation.

Y

Y

Y

2060

Skipped

1

This status means that the job was not executed at the scheduled time because either the agent was not online or was not applicable for this run.

Y

Y

N

2037

Timed Out

0

This status means that the job has timed out. The following messages are shown considering various reasons due to which the job might time out.

Messages shown for Windows Jobs:

- The job timed out because an asset reboot occurred outside the patch windows and the job also contains post-deploy actions.

- The job timed out because the patch download took the entire patching window.

- The job timed out because the action script took the entire patching window.

- The job timed out because another job is running.

- The job timed out because another job is running, and the agent didn’t download the job manifest.

- The job timed out because of the delay in providing permission to start the patch job.

Messages shown for Linux Jobs:

-  The job execution timed out.

- The CAPI call was made after the job window timed out.

- The Job timed out because another job was running.

- The job execution couldn't complete within the expected patch window. Hence it timed out.

Y

Y

Y