> The first request sent to a slept service may return a 502 Bad Gateway response.

But why...

So they won't be queued?

Serving a 502 makes the feature useless

Copy is wrong.

Not really, it's meant to be used for unimportant services, where you wouldn't care if you get a stray 502.

It's positioned as serverless though, but it doesn't work like serverless. I would totally expect cold boot times but a 502 is pretty sucky to be honest.

Between us, 'serverless' on Railway is just a catchy marketing term; it is not serverless according to the industry-recognized definition.

Well, feature request: actually queue the requests please 🙁