Users experience a critical timing and reporting discrepancy where the Unix Agent prematurely reports a job as successfully finished. Specifically:
Unix/KSH scripts executed via UC4 jobs sporadically terminate in the Automation Engine with Exit Code 0 (Ended Normally) in less than a second.
The AE job report is truncated/incomplete and stops logging prematurely.
Because the AE registers a successful completion, subsequent dependent jobs in the Job Plan trigger prematurely.
Actual Behavior: On the OS level, the executed script is still actively running. It may complete successfully seconds later, or it may fail and exit with a non-zero return code (e.g., Exit 1) which the Automation Engine entirely misses
Note: The issue is intermittent and typically affects a small percentage (~1%) of script executions under heavy production load.
Product: Automic Workload Engine
Component: Unix / Linux Agent
Version: 24.4.x
DE184202
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Unix / Linux Agent
Java-based OS agents (windows and unix) 24.4.5 - planned released June of 2026
Java-based OS agents (windows and unix) 26.1.0 - planned released June of 2026
Broadcom is evaluating an earlier fix as well, please subscribe to this article for updates.