8.3.9 Operations for interrupting step executions during debugging

When you execute a debug task, you can specify the next point to go (where step execution was interrupted) in the Debug area. The table below describes the operations to execute steps during debugging. Perform appropriate operations to proceed with debugging.

Table 8‒3: Operations for interrupting step executions during debugging
Operation	What to do	Available when:	Description	Example use case
Resume^#	Click the Resume button ().	The step is interrupted.	Resumes execution of the interrupted step. Processing starts at the point before processing of a plug-in in the nearest step with a breakpoint set and continues through to the end of the debug task.	You want to execute the debug task up to the step with a breakpoint set. You want to execute the debug task through to the end without pausing between steps.
Interrupt	Click the Interrupt button ().	The step is in progress.	Executes the step up to the nearest point at which the step can be interrupted, and then interrupts the step.	A debug task is executed by mistake without specifying step interrupts.
Step into^#	Click the Step Into button ().	The step is interrupted.	Executes the step up to the next point at which the step can be interrupted, and then interrupts the step. For a layering step, repeated step, or service step, the steps in the subordinate flow are also interrupted.	You want to proceed with debugging while checking step information before and after plug-in processing. You want to proceed with debugging while changing the step's output property values or return value.
Step over^#	Click the Step Over button ().	The step is interrupted.	Executes the step and then stops execution at the first point in the next step at which execution can be interrupted. For a layering step, repeated step, or service step, the steps in the subordinate flow are executed without interruption.	You want to perform debugging while checking the results of plug-in processing step by step. You want to perform debugging while changing input properties of the step and checking plug-in processing.
Step return^#	Click the Step Return button ().	The step is interrupted.	In most cases, this operation is used for a flow subordinate to a layering step, repeated step, or service step. This operation executes steps up to the first point at which execution can be interrupted in the upper flow and interrupts execution there. For the top-level flow, this operation executes steps to the end of the debug task.	You want to check only the first step in the repeated processing, and skip other steps.
Break points^#	To set breakpoints: Select the step for which you want to set breakpoints, and then click the Set Break Point button (). To cancel the breakpoint settings: Select the step for which you want to cancel the breakpoint settings, and then click the Set Break Point button (). To cancel all breakpoint settings: On the Break Points tab, click the Remove All Break Points button.	The Service Builder Debug window is displayed.	Sets breakpoints before and after plug-in processing in the selected step. When you perform the resume operation, step execution continues up to the breakpoint you have set.	You want to check step information before and after plug-in processing for a certain step. You want to skip plug-in processing for a certain step.

#: You can perform the same operation by right-clicking the step icon in the flow area.

The figures below display the points at which step execution is interrupted when the step-into, step-over, and step return operations are performed.

Note that if you perform the step-into, step-over, or step return operation, [Figure] appears on the icon of the next step in the flow area.

If step-into operation is repeated after the debug task started

Figure 8‒6: Points at which execution is interrupted by step-into operation

Step execution is interrupted before and after processing of all plug-ins including those subordinate to the flow plug-in. However, execution cannot be interrupted after the flow plug-in has started. Therefore, execution is interrupted before plug-in processing of Step E, rather than after plug-in processing of Step B.

If step-over operation is repeated after the debug task has started

Figure 8‒7: Points at which execution is interrupted by step-over operation

Execution is interrupted before plug-in processing of each step. However, execution of steps is not interrupted in the flow that is subordinate to the flow plug-in.

If step-return operation is performed for the flow subordinate to the flow plug-in

Figure 8‒8: Points at which execution is interrupted by step-return operation

After all steps in the flow subordinate to the flow plug-in are executed, processing returns to the upper-level flow, and then execution is interrupted before plug-in processing of Step E.