Request ID : G946lcEJQK6yluZem3z_FQ

NONE of the http request appears in the service dashboard during "bug"

Seeing that it’s in a “sleeping” state, have you tried disabling serverless in service settings?

The features helps me saves a lot of ressources, I can do that but it doesn't fix the bug that it doesn't receive ANY request for an extended amount of time

and the moment I redeploy another instance, all the request that it should have received appears in the HTTP log

And I assume hitting any of the endpoints doesn’t wake it up right?

yep

Unless i manually redeploy it and it works fine for some days until it doesn't

The instance has been "down" for 4 hours today

With 502 bad gateaway errors

It stopped** getting requests starting 8:42 GMT+1 until 12:42 GMT+1 when I redeployed another instance

I removed the serverless option, unless there is an explaination for the origin of the issue, I will start looking for a different service.

> Slept services still consume a slot on our infrastructure, enabling Serverless de-prioritizes your workload and in remote cases, may require a rebuild to re-live the service.

I don't see how this is relevant to the discussion

You will sometimes need to redeploy a sleeping service.

Manually redeploy it ?

Correct.

Serverless is not meant for anything production related.

It isn't written anywhere that Serverless isn't meant for anything production related but ok, it's noted.