Handling interruptions of debug tasks

Ops Center Automator Service Builder User Guide

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

Under specific circumstances, the tasks might be interrupted or ended in unexpected ways during a debugging session.

The steps in the debug task appear in the Flow view of the service template debugging view in the order in which they run. The icon of the step indicates the status of the step. You must be aware of how tasks are affected when the debugging process is interrupted.

Handling of debug tasks when the Ops Center Automator server stops

If the Ops Center Automator server stops during debugging, the debug task that is running is forcibly stopped. Therefore, before stopping the Ops Center Automator server, wait for all debug tasks that are still running (not yet completed) to finish or stop the debug tasks. This is the same as the handling of tasks generated when normal services are run.

Handling of debug tasks when a failover of the cluster occurs

When a cluster failover (switchover of the system) occurs during debugging, the debug task is forcibly stopped. This is the same as the handling of tasks generated when normal services are run.

Handling of debug tasks when the user logs out during debugging

When a user logs out during debugging, a confirmation dialog box appears asking for confirmation before logging out the user. If you choose to log out, the debug task is forcibly stopped.

Handling of debug tasks when the browser is closed

When the browser is closed during debugging, the debug task continues running normally. If the task is running step-by-step, the task remains at the step where it stopped. To stop the debug task, you must log on again and then stop the debug task from the Debug Task List view.