Jobs stuck as no workers are being initialized
I have an endpoint that is not spinning workers anymore even when I try resetting the number of max/active workers.
5 Replies
Endpoint ID: b6lk6eiyakxwvc
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
I ended up changing CPU from 5Ghz to 3Ghz, it was an issue with worker availability but nothing pointed to that so..
Also, I am disappointed with this experience. This was a production endpoint, and the issue has negatively impacted our professional standing with the client.
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
Yes, it involved two endpoints that suddenly lost all available workers. There have been no code changes or updates for over a month, so it came suddently with no prior warning.