When Windows agent executes check and the device goes to sleep, the check execution times out upon waking up, causing ACC-2100 errors to be logged - Known Error

When Windows agent executes check and the device goes to sleep, the check execution times out upon waking up, causing ACC-2100 errors to be logged Description A check executed on a Windows agent will time out if the Windows device goes to sleep while the check is executing. This will cause ACC-2100 errors to be created.

The timeout happens because of a golang bug where go's built-in timer functionality does not subtract off OS sleep time from the elapsed time, causing the timer to fire immediately after the device wakes up.

Steps to Reproduce

1. Execute a check on Windows agent that takes some time to execute, say 2 minutes, with a 5 minute timeout. 2. Make the Windows host go to sleep (close laptop lid or Sleep in the start menu) 3. Wait 5 minutes. 4. Wake up the Windows host. Actual: Upon waking up, the check execution times out immediately, sending an "Execution timed out" response to the Instance, and an ACC-2100 error will be logged

Expected: Upon waking up, the check execution should continue executing without timing out. It should take the OS sleep time into account before timing out.

Workaround No possible workaround.

However, ACC-2100 errors will be resolved if the check that failed is successfully executed sometime in the future. This means that ACC admin can wait for the check to execute again, although there is always some chance that the Windows device sleeps during subsequent executions.