a month ago
My service uses the serverless feature but the cold requests always show the "application failed to respond" message instead of waiting for the deploy.
Project ID: b90bdfe3-0a20-4f0e-8c2e-e55e7e31f592
10 Replies
a month ago
> The first request sent to a slept service may return a 502 Bad Gateway response.
a month ago
But why...
Attachments
a month ago
Copy is wrong.
a month ago
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.
a month ago
Between us, 'serverless' on Railway is just a catchy marketing term; it is not serverless according to the industry-recognized definition.