Task issues

This topic describes how to recover your environment if task issues occur.

You may encounter tasks issues while using HCL Universal Orchestrator. In this topic you can find the main problems and the related solutions.

Tasks remain in READY status

If a task remains in READY status and does not start, the reason is that the workstation is offline or stopped. When the workstation is online again, the task starts automatically.

Tasks do not appear in the plan

If a task does not appear in the plan, there are different possible reasons:

The instance of the task has not been created yet in the current plan

Save the workflow definition again.

The future instance did not activate

Save the workflow definition again.

The active-window policy value is too short

If the active-window value is too short, you can set another value for the policy inside the values.yaml file:

uno.planning.active-window=24:00:00

For more information, see HCL Universal Orchestrator policy-driven plan.

The active-window.extension policy value is too large

If the active-window.extension value is too large, you can set another value for the policy inside the values.yaml file:

uno.planning.active-window.extension=00:05:00

For more information, see HCL Universal Orchestrator policy-driven plan.

Executable task failure: Method not found addexecutableParameters

HCL Universal Orchestrator comes with the built-in executable task. The executable task enables you to create executable tasks in the Graphical Designer.

If you upgrade HCL Universal Orchestrator from V1.1.0 to V1.1.2 or later, or from V1.1.1 to V1.1.2 or later, a new executable task is installed. You must manually delete the previous version of the executable task to avoid executable task failures.