Users may observe an apparent mismatch between the number of active jobs displayed in the Monitoring Queue and the slot usage reported in the Administration Area.
Component: Automation Engine
Version: 24.4.0 and higher
This behavior is By Design.
The discrepancy arises from how the engine handles Workflow (JOBP) slot allocation versus Child Task allocation. When a workflow is triggered, the system evaluates slot availability for both the parent container and the subsequent tasks.
Specifically:
One slot is occupied by the Workflow itself.
Additional slots are reserved for Tasks within that workflow as they are prepared for execution.
The internal flag EH_QueueSlotOK is set to 1 to ensure tasks can start immediately upon release.
In previous versions, a bug caused the system to over-count (e.g., jumping to 3 slots for a 2-slot operation). In version 24.4.0, the counting logic has been corrected to reflect actual reservations, which may still result in "In Use" counts exceeding the "Active Job" count if multiple tasks are queued for immediate start.