1.6.8 Step statuses

The Flow area provides a graphical representation of the steps in a task, allowing users to see how far a task has progressed. If an arrow conditional-expression is specified for a step, an icon indicating the arrow status will be displayed. Step statuses and their corresponding icons are shown in the table Step statuses and their descriptions, and arrow statuses and their corresponding icons are shown in the table Arrow statuses and descriptions.

Table 1‒8: Step statuses and their descriptions
No.	Category	Step status	Description
1	Waiting	Waiting	This status applies to: Steps whose task has been generated but has not started executing Steps that are waiting for the preceding step to finish
2	Waiting	Waiting for Loop Execution	This status indicates that a step or repeated execution flow under a Repeated Execution Plug-in is waiting to be executed. For example, this status applies in the following circumstances: Before a Repeated Execution Plug-in is executed When a step in a Repeated Execution Plug-in has been skipped by the debugger function When a task stops before a Repeated Execution Plug-in When a step is waiting because the maximum number of concurrently executable steps^#1 has been reached during repeated execution
3	Running	Interrupted	This status indicates that the step was interrupted immediately before plug-in processing started.
4		Interrupted (After progressing)	This status indicates that the step was interrupted immediately after plug-in processing finished. This status appears when debugging service templates.
5		In Progress	This status indicates that the plug-in processing is being executed.
6		Waiting for Input	This status indicates that plug-in process requires input from a user.
7		Completed (With Error)	This status indicates that a succeeding step was executed after an error occurred in one or some of the plug-ins in the flow.
8	Stopped	Completed	Indicates that the corresponding step has finished normally.
9		Failed	Indicates that the corresponding step did not finish normally. For example, a Failed status might result when: The corresponding step is stopped because an error occurred JP1/AO has stopped a step in response to a user request The return value was deemed abnormal on the basis of the subsequent-step execution condition.
10		Failed	A status indicating that the corresponding step ended with a warning on the basis of the subsequent-step execution condition.
11		Unexecuted	A status indicating that the corresponding step was not executed^#2.
12		Bypassed	A status indicating that the corresponding step was not executed because it represents a step not taken by a plug-in that judges a value or return code.

#1: You can change the maximum number of concurrently executable steps during repeated execution by editing the user-specified properties file (config_user.properties).

#2: Does not include steps that were skipped because a branch by return code Plug-in or branch by property value plug-in selected an alternative flow.

Depending on the step status and plug-in type, some step statuses might not be displayed. The following table shows which statuses are displayed for each type of step.

Table 1‒9: Step statuses and whether they are displayed
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 for Loop Execution	Y^#	N	Y	Y^#
3	Running	Interrupted	N	Y	N	Y
4		Interrupted (After progressing)	N	N	N	Y
5		In Progress	Y	Y	Y	Y
6		Waiting for Input	N	N	N	Y
7		Completed (With Error)	Y	N	Y	N
8	Stopped	Completed	Y	Y	Y	Y
9		Failed	Y	Y	Y	Y
10		Failed	Y	Y	Y	Y
11		Unexecuted	Y	Y	Y	Y
12		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 for Loop Execution status.

Table 1‒10: Arrow statuses and their descriptions
Arrow status	Description	Icon
TRUE	This status indicates that the corresponding step matches conditions for execution.
FALSE	This status indicates that the corresponding step does not match conditions for execution.
NOT YET	This status indicates that the corresponding step was not executed.