When an operation is submitted, the Job Orchestrator attempts to locate a compliance node with sufficient available resources to execute the operation.

For complex and long-running operations, such as compliance job executions, the system validates the operation against two primary resource limits.

Maximum number of simultaneously running operations

The maximum number of operations that can run simultaneously on a node is controlled by the NumSimulOperationsAllowedPerNode application setting.

The default value is 7.

To modify this setting, see Job Orchestrator Application Settings.

Maximum memory for running operations

The system also evaluates the total memory required for running operations on the node.

By default, the maximum memory available for operations is calculated dynamically using the following formula:

75% of the node's available memory − 6 GB

The remaining 6 GB is reserved for system processes.

This limit can be manually overridden using the MaximumMemoryForJobsPerNode application setting.

If a manual value is configured, the system will use that value instead of the dynamically calculated limit.

To restore the dynamic calculation, set MaximumMemoryForJobsPerNode to 0.

Operation queueing

If a submitted operation would cause all registered nodes to exceed either of these limits, the operation is placed in a queue.

Queued operations will automatically start when sufficient resources become available after other operations complete.

Not all operations support queueing. Certain operations are synchronous and require immediate access to a node. These operations will execute on any node that is currently ONLINE.

View queued operations

To view the position and details of queued operations:

  1. Navigate to the Job Orchestrator details page.

  2. Open the Queued Operations tab.

This view displays all operations currently waiting for available resources.

Abandon a queued operation

If a queued operation needs to be canceled, the associated PENDING operation must be abandoned.

To abandon an operation:

  1. Locate the operation in the Queued Operations tab.

  2. Select the View link to open the operation details.

  3. Click Actions > Abandon.

You can also access the operation through the Operations page under the Admin navigation menu.

If a queued operation must be stopped before execution begins, the pending operation must be abandoned. Otherwise, the operation will remain in the queue until system resources become available.
Last updated
Oct 8, 2026