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.
No description
5 Replies
inc3pt.io
inc3pt.ioOP2w ago
Endpoint ID: b6lk6eiyakxwvc
Jason
Jason2w ago
Can you clone the endpoint instead?
inc3pt.io
inc3pt.ioOP2w ago
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.
Jason
Jason2w ago
i see can you try to open a ticket for this just curious, so this endpoint suddenly the worker dissapears?
inc3pt.io
inc3pt.ioOP2w ago
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.

Did you find this page helpful?