Activity Log Shows "Command timed out" 

The "COMMAND TIMED OUT" error typically indicates that a policy or process took longer than expected to execute. Below is an explanation of what it means, its potential causes, and how to resolve it.

Common Causes of "COMMAND TIMED OUT"

1. Policy Execution Delays:
   • The patch policy did not finish installation within the expected timeframe.
     1. Example: The Automox agent initiates a Windows Update that takes too long to complete, resulting in a timeout.
2. Worklet Timeout:
   • A Worklet on a Windows device exits with an "exit 1" status, which Automox translates to "exit 124" or "COMMAND TIMED OUT."

Troubleshooting Steps

1. Check Windows Update Logs:
   • Follow Microsoft's guide to retrieve the logs.
2. Verify Software Installation:
   • Even if the error appears, check if the software was successfully installed.
3. Avoid Using Exit Code 1 in Worklets:
   • To prevent misinterpretation as "COMMAND TIMED OUT," use an alternative exit code for Worklets.