1.6.13 Step statuses

In the Task Monitor view, you can visually check how far steps of the running task in a flow have been processed. The following table describes information that is displayed as step statuses.

Table 1‒14: Step statuses and their descriptions
No.	Category	Step status	Description
1	Waiting	Waiting	This status applies to: Tasks that are generated but have not started executing Waiting for the previous step to finish
2	Waiting	Waiting to Repeat	This status indicates that steps or repeated execution flows under the recurring plug-ins are waiting for the next execution. For example, this status applies to the following cases: Before a recurring plug-in is executed When a step for a recurring plug-in is skipped by the debugger function When a task stops before a recurring plug-in Waiting status when a step exceeding the maximum number of steps that can be executed concurrently^#1 is executed during recurring execution
3	Running	Interrupted	Indicates one of the following statuses: Interrupted immediately before processing of a plug-in starts Interrupted immediately after processing of a plug-in ends
4		Now Running	Indicates that the plug-in is being processed.
5		Waiting for Response	Indicates that the processing of a plug-in requires a user response.
6		Abnormal Detection	Processing of some plug-ins detects an error, but the subsequent steps are in progress.
7	Stopped	Completed	Indicates that the corresponding step has finished normally.
8		Failed	Indicates that the corresponding step has not finished normally. For example, a failure occurs when: The corresponding step was stopped because it detected an error. A user stopped a task, and the stop processing is completed. A return value is judged to have ended abnormally with the condition for executing subsequent steps.
9		Ended with a Warning	Indicates that the corresponding step detected a warning and stopped due to subsequent execution conditions.
10		Not Executed	Indicates that the corresponding step has not been executed.^#2
11		Bypassed	Indicates that the corresponding step was not executed because a plug-in did not branch off.

#1: Specify the maximum number of steps that can be executed concurrently during recurring execution in the property file (config_user.properties).

#2: Exclude steps that were not executed because a flow was branched in the judge return code plug-in or judge value plug-in.

Note that depending on the step status or plug-in type, some step statuses might not be displayed. The following table shows the step statuses and the display of each step.

Table 1‒15: Step statuses and display of each step
No.	Category	Step status	Layering step (flow plug-in)	Repeated step	Repeated execution flow	Normal step
1	Waiting	Waiting	Y	Y	Y	Y
2	Waiting	Waiting to Repeat	Y^#	N	Y	Y^#
3	Running	Interrupted	N	Y	N	Y
4		Now Running	Y	Y	Y	Y
5		Waiting for Response	N	N	N	Y
6		Abnormal Detection	Y	N	Y	N
7	Stopped	Completed	Y	Y	Y	Y
8		Failed	Y	Y	Y	Y
9		Ended with a Warning	Y	Y	Y	Y
10		Not Executed	Y	Y	Y	Y
11		Bypassed	Y	Y	N	Y

Legend:: Y: Displayed, N: Not displayed

#: If the step is under a repeated execution plug-in, the step enters Waiting to Repeat status.

Related topics

Property file (config_user.properties) in the Job Management Partner 1/Automatic Operation Configuration Guide

To Page Top