a month ago
Project 49e739bd-587c-4d35-8be7-2c985e1018c8
Service 0a02ddfc-5913-4e84-961f-dc8888af5ca8
Plan: 8 GB / 8 vCPU, single replica, Southeast Asia (Singapore)
My service streams large file archives to the browser as a single HTTP response. The response is built and sent progressively, so data flows continuously from the first second to the last. The 5-minute inactivity limit is therefore not a factor.
The constraint is the 900-second total request timeout. Longer exports are cut off mid-stream, which leaves the customer with an incomplete file rather than a failure they can retry cleanly.
Three questions:
-
Can the 900-second request timeout be raised for this service? If so, what is the maximum, and is it a per-service setting or a plan attribute?
-
If it cannot be raised on my current plan, is there a plan where it can be, and what is the limit there?
-
Is there a supported way to serve a long-running download that is not subject to this ceiling? I am aware websockets are exempt, but that is not a natural fit for a file download the browser's own download manager should handle.
If any of this needs to go through a private or billing channel, please tell me where to send it.
Pinned Solution
a month ago
Hey, the 900 second limit is Railway's maximum, it's not configurable on a per-service basis and you cannot raise it further (It cannot be raised by switching plans).
I've seem some people switch to WS so they have some sort of unlimited duration.
4 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
0x5b62656e5d
I’d recommend splitting the large file into multiple parts instead.
a month ago
Thank you, but that does not answer what I asked. I understand splitting into parts is one approach and it is on our list; I need to know the constraint before choosing between it and the alternatives.
Specifically:
-
Can the 900-second request timeout be raised for this service, yes or no? If yes, to what maximum, and is it per-service or a plan attribute?
-
If not on my current plan, is there a plan where it can be?
A direct yes or no on question 1 is what I need. If the answer is that it cannot be raised on any plan, please say so and I will design around it.
a month ago
Hey, the 900 second limit is Railway's maximum, it's not configurable on a per-service basis and you cannot raise it further (It cannot be raised by switching plans).
I've seem some people switch to WS so they have some sort of unlimited duration.
medim
Hey, the 900 second limit is Railway's maximum, it's not configurable on a per-service basis and you cannot raise it further (It cannot be raised by switching plans). I've seem some people switch to WS so they have some sort of unlimited duration.
a month ago
Thank you, that is exactly what I needed. A clear no on raising it, and confirmation it is not plan-dependent, is enough for me to design around it. Appreciate the direct answer.
Status changed to Solved 0x5b62656e5d • about 1 month ago