Displaying Task Instance Status

You can display the status of one or more task instances from the Activity Monitor, Task Instances list, History list, or Command Line Interface (CLI).

Activity Monitor	To display the status of one or more task instances on the Activity Monitor: From the Automation Center navigation pane, select Task Instances > Activity. The Activity Monitor contains a Status column that identifies the current status of every task instance on the list.
Task Instances list	To display the status of one or more task instances on the Task Instances list: From the Automation Center navigation pane, select Task Instances > All Task Instances. The Task Instances list contains a Status column that identifies the current status of every task instance on the list.
History list	To display the status of one or more task instances on the History list: From the Automation Center navigation pane, select Task Instances > History. The History list contains a Status column that identifies the current status of every task instance on the list.
Command Line Interface (CLI)	To display the status of one or more task instances from the Command Line Interface: Use the ops-task-status function.

Task Instance Status Types

The following table describes all possible task instance statuses for all task types.

For a list of commands that you can issue against a task instance in each status, see Commands Supported for Task Instance Statuses.

For a description of each command, see Issuing Commands Against Task Instances.

Note

The format of multi-word task status names used in the Controller user interface differs from the format of task status names specified in the Display Task Instance Status CLI function. In the user interface, they are separated by a space; in the Display Task Instance Status CLI function, the words are separated by an underscore character.

Status Code	Status Name	Task Type	Description
0	Defined	All	The new task instance has been created (the task has been launched).
10	Waiting	All	The task instance has been loaded by a workflow and is waiting on a predecessor.
15	Time Wait	All (except Timer)	The task instance is waiting to start based on a Wait To Start and/or Delay On Start specification.
17	Instance Wait	All	The task instance has been loaded by a workflow and is waiting on a previous instance(s) of the same task based on the Instance Wait Resolved specification.
20	Held	All	The task instance has been put on hold by a user.
22	Exclusive Requested	All	All task instances with a mutually exclusive task defined go immediately to a status of Exclusive Requested. If the task instance is available to run exclusively, the task instance then moves to the next appropriate processing status.
23	Exclusive Wait	All	The task instance is mutually exclusive with one or more other task instances, and it is waiting for those task instances to finish before it will run.
25	Resource Requested	All	All task instances with a virtual resource defined go immediately to a status of Resource Requested. If the resource is available, the task instance then moves to the next appropriate processing status.
30	Resource Wait	All	All task instances with a virtual resource defined go immediately to a status of Resource Requested. If the resource is not available, the task instance goes to a status of Resource Wait. When the resource becomes available, the task instance moves to the next appropriate processing status.
33	Execution Wait	Agent-based	The task instance must wait to be completed; either the Agent/Agent Cluster running the task instance has reached its Task Execution Limit, or the ability of the Agent/Agent Cluster to run tasks has been suspended.
35	Undeliverable	Agent-based	The Agent is unavailable.
40	Queued	Agent-based	The task instance has been queued on a resource.
43	Submitted	z/OS	The task instance has been submitted to the z/OS Job Entry subsystem and scheduled by the z/OS Job Scheduler.
45	Step Restarted	z/OS	The task instance has been re-run starting from a specific z/OS jobstep.
60	Action Required	Manual	When a Manual task launches, the task instance goes into Action Required status, meaning a user must perform some manual activity. For details, see Manual task.
70	Started	Agent-based, Manual	The task instance has started. For Agent-based tasks, this means the Agent has received the task.
80	Running	All	The task instance is running. For Agent-based tasks, the Agent has started running the program.
81	Running/Problems	Workflow	One or more task instances within the workflow has one of the following statuses: Cancelled Confirmation Required Failure In Doubt Running/Problems (for sub-workflows) Start Failure Undeliverable
99	Cancel Pending	Agent-based	A process running on the Agent needs to be terminated. When the Cancel command is issued, the task instance will go into a Cancel Pending status until the Agent reports back that the process has been cancelled. At that point, the task instance will transition into the Cancelled status.
110	In Doubt	Agent-based, SQL, Stored Procedure, Web Service	The task instance is "in doubt" about the current status of the job. This may occur if an Agent or Agent connection goes down. In this case, the Agent restarts and reviews its data about task instances in progress. If the Agent finds a task instance still running, it resumes normal monitoring. If the Agent cannot find the task instance, this usually indicates that the task instance completed, but the Agent considers the task instance status to be "in doubt." When the Controller restarts, any SQL, Stored Procedure, and Web Service task instances that are in a Running status will transition into the In Doubt status, since the Controller no longer has any knowledge of them.
120	Start Failure	All	The task instance was unable to start.
125	Confirmation Required	z/OS	If you make JCL changes and restart a z/OS task instance, Universal Controller will put the task instance into Confirmation Required status and prompt you for a confirmation. For detailed processing steps, see Rerunning a z/OS Task.
130	Cancelled	All	The task instance was cancelled by a user.
140	Failed	All (except Workflow)	The task instance ran to a failure status.
180	Skipped	All	The task instance was skipped by Run/Skip criteria, an Execution Restriction, or the Skip command.
190	Finished	All	The task instance was forced by the user to finish. The user may do this in cases where the task instance had a Cancelled or Failed status, and the user needed to release other task instances depending on the successful completion of this task instance in a workflow. For more information, see Force Finishing a Task.
200	Success	All	The task instance has completed successfully. Workflows will transition to Success status when all of its task instances have transitioned to Success, Finished, or Skipped status.

Agent-Based Task Types

The following task types are Agent-based task types:

Linux/Unix
Windows
z/OS
Universal Command
SAP
PeopleSoft
File Transfer
Agent File Monitor
Remote File Monitor
System Monitor
Universal

Task Instance Status Colors

You can change the default color assigned to each task instance status via the Colors, in the Reporting navigation pane.

Browser not supported