You can implement a workflow to monitor long-time operations that your Orchestrator plug-in performs.

You can implement a workflow for monitoring long-time running operations such as task monitoring. This workflow can be based on Orchestrator triggers and waiting events. You must consider that a workflow that is blocked waiting for a task can be resumed as soon as the Orchestrator server starts. The plug-in must be able to get all the required information to resume the monitoring process properly.

The monitoring workflow or the task that it can use internally should provide a mechanism to specify the pooling rate and a possible timeout.

The process of debugging a piece of scripting code inside a workflow is not easy, especially if the code does not invoke any Java code. Because of this, sometimes the only option is to use the logging methods offered by the default Orchestrator scripting objects.