Welcome
Monitoring
Take your environment under control.
Orchestration Monitor overview
The Orchestration Monitor gives you granular control over your plan, enabling you to take direct action over every item.
Viewing the run context of a task
In the Orchestration Monitor, you can inspect the full JSON context recorded during a specific task run to troubleshoot data flow issues and validate runtime values.

What's new
The What's new section tracks the capabilities delivered across each HCL Universal Orchestrator release, organized by version, so you can navigate directly to the features relevant to your deployment.
Getting started with HCL Universal Orchestrator
HCL Universal Orchestrator is a cloud-native workload orchestration and scheduling platform built on Kubernetes. Its microservices-based architecture enables the centralized orchestration of multi-cloud and hybrid environments from a single point of control.
Deploying and Administrating
All the information you need to deploy and administrate HCL Universal Orchestrator.
Using the UI
The UI is the HCL Universal Orchestrator interface, from which you can design your scheduling environment and monitor every process.
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Orchestrating from Mobile
You can use your mobile devices to manage quickly and easily your whole HCL Universal Orchestrator environment.
Monitoring
Take your environment under control.
- Orchestration Monitor overview
  The Orchestration Monitor gives you granular control over your plan, enabling you to take direct action over every item.
  - Orchestration Monitor scenario
  - Viewing the run context of a task
    In the Orchestration Monitor, you can inspect the full JSON context recorded during a specific task run to troubleshoot data flow issues and validate runtime values.
- Monitoring from the Orchestration CLI
- Monitoring your workload with dashboards
  Dashboards provide a centralized view to monitor the health, status, and progress of your workload.
- Using Orchestration Query Language
  You can use the essential Orchestration Query Language (OQL) keywords and syntax to effectively write queries.
- Sub statuses for tasks and workflows
  The sub statuses within the primary status of tasks or workflows provide additional context and granularity.
Using REST API
Use REST APIs to easily integrate workload scheduling capabilities with external products and solutions.
Administering multitenancy for service providers
Configure and administer a HCL Universal Orchestrator multitenant environment.
Uno AI Pilot
Welcome to the HCL Universal Orchestrator AI Pilot documentation. This resource is designed to guide you through everything you need to know about using UnO AI Pilot effectively. You will find detailed instructions, feature overviews, and helpful tips to ensure you get the best experience with UnO AI Pilot.
UnO Agentic AI Builder
Troubleshooting
Recover your environment if any issue occurs.
Notices

v2.1.5+ Viewing the run context of a task

In the Orchestration Monitor, you can inspect the full JSON context recorded during a specific task run to troubleshoot data flow issues and validate runtime values.

About this task

Each task run records its full JSON context at run time. The context captures the complete state of the task as it ran, including return codes, variables, workflow metadata, and the output of predecessor tasks. You can inspect this context directly from the Orchestration Monitor without re-running the workflow.

Access to the task context is restricted to users authorized to view the corresponding plan item. Plan item authorization covers the complete run-time snapshot: if you can view a plan item, you can see all variable values resolved during that run, including values sourced from variable tables that you do not have direct access to.

Procedure

Open the Orchestration Monitor.
Navigate to the Tasks view and locate the run instance you want to inspect.
Open the task details panel and click View JSON Context.
The context viewer opens and displays the full JSON context recorded for that run.
Use the viewer controls to inspect the context data:

Copy to clipboard

Copy the full context JSON to paste it directly into the JSONata editor for expression testing.

Results

The context viewer displays the JSON object as it existed at the time of the selected run. The top-level properties of the context are:

RC: The return code of the task.
var: The key-value pairs representing workflow variables.
js: The workflow metadata, matching the JobStreamInPlanV2 schema.
jobs: The task-level data, including output properties from predecessor tasks, matching the JobInPlanV2 schema.

For the full schema reference, see Task context structure.

What to do next

To test JSONata expressions against this context, open the JSONata editor from any JSONata-capable field in the Graphical Designer and load the context from a previous run. You can also copy the context JSON from this viewer and paste it manually into the editor.