Long-running HTTPS request
ryanhaticus
HOBBYOP

2 months ago

I have an Express server endpoint that makes a bunch of synchronous operations and returns a result to a frontend. That said, this takes sometimes a few minutes to complete and the Railway proxy sometimes returns "Application failed to respond" even though the process is still ongoing.

Any way to disable this or increase the timeout threshold?

0 Replies

ryanhaticus
HOBBYOP

2 months ago

Realistically, I could have implemented this with a queue of sorts and made it async, but I'm lazy.


passos
MODERATOR

2 months ago

for how long your request keeps running?


ryanhaticus
HOBBYOP

2 months ago

I can time the next one. Response probably isn't sent for ~90 seconds on average.


passos
MODERATOR

2 months ago

that shouldn't be an issue for Railway then as the timeout is 15 minutes


noahd
EMPLOYEE

2 months ago

Howdy!
Railway's timeout is 15 minutes for HTTP requests.
The How it Works section of public networking mentions this in Edge Traffic 😁


Loading...