Controlling the processing flow of debug tasks

Ops Center Automator Service Builder User Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99AUT002-18

The following describes the general procedure for debugging a service template.

A service template in the Developing state must exist with steps you added to the Flow view.
  1. If you do not expect any problems when running the plug-ins in the service template, the first step of the debug process is to run the debug task without pausing between steps. In the Debugger view or the service template debugging view, make sure that there are no problems with the flow transitions or the plug-in processing. If the service template contains plug-ins that you do not want to run at this time, skip this step and move directly to step 2.
  2. If you identify an problem with a flow transition or plug-in processing, run the steps in the debug task individually to identify the precise location and nature of the problem. You can also test the behavior of the plug-ins by assigning unexpected values to input and output properties.
    • Click Step Into to run the currently selected step.
    • Click Step Over to run the next step.
    • Click Step Return to run the step in the upper flow after completing the steps in the current flow.
    • To start the debugging process start again from the failed step, click the debug arrow, and choose Retry the Task Starting from the Failed Step. By trying again from a failed step, you can resume the debug task with the same task ID and the original property values. You can use this approach when the cause of the failure is resolved. For example, you can try a step again that fails because of a temporary problem with the network when the network connection is available again.
    • To start the debugging process again from the step after the failed step, click the debug arrow, and choose Retry the Task Starting from the Step after the Failed Step. By retrying from the step after the failed step, you can resume the debug task with the same task ID and the original property values. This approach is best in situations where there is no must to run the failed step. When you try a task again from the step after the failed step, the task processing continues as if the failed step ended normally. You can use this approach when you encounter an problem in a step, but want to continue running the debug task and handle the problem later.