Timeout errors at 100 seconds
The docs say 900 second timeout, I've also seen 5 min throughout the forums but I'm seeing 100 seconds where the client closes the request with a status of 499.
https://railway.app/project/d1209c25-de11-43b5-b139-49cb997e4056/service/610e48a4-88a4-4b93-b233-cb497bab0dc1?id=83c17dc7-2bb2-4c0b-abd7-323095a0cfa5#http
It's a simple node app (endpoint /start). Any idea how I can debug this and resolve it? Is the max timeout configurable?
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
Solution:Jump to solution
A status code of 499 means the client closed the connection prematurely, not railway
8 Replies
Project ID:
d1209c25-de11-43b5-b139-49cb997e4056,610e48a4-88a4-4b93-b233-cb497bab0dc1,83c17dc7-2bb2-4c0b-abd7-323095a0cfa5
Solution
A status code of 499 means the client closed the connection prematurely, not railway
Ok I’ll play around with my app config
should that route take longer than 1 second?
Got it, it was Cloudflare. And yes it's a long running job. Working on make async but for now this is worling.
awsome!
Thanks for the help!