We’ve seen this a few times, but the machine policy was caught today running for the past 25hrs! Stuck on one machine and doing nothing apparently. On cancelling we see the kill command going down and eventually it cancels the task successfully:
Bug or just one of those things?
Sorry that it’s taken so long for me to respond to this one!
This is something that we have been working on, and should be improving over time. Please let me know if this is still a problem for you and we can look into if further!
No issues found this week, so looking good!
That’s great news, thanks for letting me know!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.