22 days 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
22 days ago
> The first request sent to a slept service may return a 502 Bad Gateway response.
22 days ago
But why...
Attachments
22 days ago
Copy is wrong.
22 days 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.
22 days ago
Between us, 'serverless' on Railway is just a catchy marketing term; it is not serverless according to the industry-recognized definition.