Skip to content

docs(serverless): first request 502 bad gateway response caveat #1144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brody192 merged 2 commits into from
May 11, 2026
+2 −1
Merged

docs(serverless): first request 502 bad gateway response caveat #1144

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9e28325
docs(serverless): first request 502 bad gateway response caveat
uxuz May 8, 2026
a25e49d
docs(serverless): potential 502 bad gateway response as its own caveat
uxuz May 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion content/docs/deployments/serverless.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,8 @@ The first request made to a slept service wakes it. It may take a small amount o

## Caveats

- There will be a small delay in the response time of the first request sent to a slept service (commonly known as "cold boot times")
- There will be a small delay in the response time of the first request sent to a slept service (commonly known as "cold boot times").
- The first request sent to a slept service may return a 502 Bad Gateway response.
- For Railway to put a service to sleep, a service must not send _outbound_ traffic for at least 10 minutes. Outbound traffic can include telemetry, database connections, NTP, etc. Inbound traffic is excluded from considering when to sleep a service.
- Enabling Serverless will apply the setting across all [Replicas](/deployments/scaling#horizontal-scaling-with-replicas)
- Slept services still consume a slot on Railway's infrastructure, enabling Serverless de-prioritizes your workload and in remote cases, may require a rebuild to re-live the service.
Expand Down
Loading