What do you mean by “disable itself”? Workers will spin up and down as needed based on traffic and requests. If your Worker doesn’t get any traffic for a while, it’s very possible it’ll be evicted from memory and require a cold-load on the next request. This shouldn’t add much more than a handful of miliseconds to your response time though.
Can you shed any more light on what exactly is happening?
Sure, that’s what I assumed but the worker doesn’t activate immediately when it receives a new request, it usually takes about 5-10 min to respond to the requests.
When I say “disable itself” I mean that for no apparent reason the worker stops responding to the request, in fact in the logs of the worker the request does not appear.