File event stuck in sleeping after agent reconnection
Article ID: 406224
Updated On:
Products
Issue/Introduction
When an Automic agent is reconnected (perhaps restarted or during an upgrade) while a File Event is active, the event may become permanently stuck in a "Sleeping" status. This issue can occur during routine maintenance, such as OS patching, or during a manual restart of the agent service. The event fails to re-evaluate its conditions and does not trigger, even after the agent has successfully reconnected to the Automation Engine.
Analysis of agent log files shows that during a graceful shutdown, the agent ends the file event thread and removes the event from its internal processing list, logging a message similar to U02000162 Event '[RunID]' was removed from event list. After the agent restarts, the Automation Engine does not appear to re-initiate the event check, causing the event object to remain indefinitely in the "Sleeping" state, requiring manual intervention to cancel and restart it.
Environment
This behavior has been observed across multiple versions, including 12.3, 21.x, and 24.x.
Cause
This is caused by a known issue
Resolution
This issue was fixed with Automation Engine version/service pack 21.0.10 and 24.1.0. Please note that an upgrade to these versions will require the AutomationEngine, AWI, Utilities, and initialdata to be on at least the same service pack.
Additional Information
AE-36394: A bug was fixed where file events were not correctly restarted on agent disconnect and reconnect.
Feedback
