Jobs getting stuck in agent queue - fix found

whenever we kick off Jobs against an agent they’re not running and instead get stuck in the queue for that agent. We’ve tried restarting agents and having no luck. Anyone else having this issue?

1 Like

we have a found a fix for this - deleting the agent and then registering it again - Jobs appears to be working again now

I have the same issue but for tests in stead of jobs and by starting them through the API.
All is well and the test should be started, but as you say, it ends up being queued.
Deleting and reinstalling the agent seems like an interesting fix.
Thanks for sharing your findings.

1 Like