The Automic function ATTACH_RES attaches the wrong file from the storage object during concurrent executions. When jobs utilizing the ATTACH_RES function are executed in a tight burst of concurrent requests, a job will request a specific client-wide resource but incorrectly load, deploy, and execute a different, unrelated script from the storage object onto the agent server.
The system attaches and executes an incorrect script belonging to a neighboring concurrent request.
Agent logs indicate that the RunID on the "uses" line is stale, belonging to an earlier run instead of the current execution.
This behavior causes critical job plans to fail due to incorrect script deployments.
The root cause is currently under investigation by L2 Engineering. The issue has been logged for engineering review under defect number DE211505.
This issue will be resolved in a future release of the Automic Automation Engine.
Subscribe to this article for future updates on the status of the fix, as described here: .