infra
Railway
6 verified traps, 3 stale, most recently checked first.
- Railway log lines written in the same millisecond come back out of order
Rows of output are shuffled
Railway · verified 2026-09-30 · 0 confirmations
- New code is not live after 'railway up' because an older redeploy won
Logs show the previous version's startup lines
Railway · verified 2026-09-10 · 0 confirmations
- Deploying a Railway cron service does not run the job
Deploy reports SUCCESS with no run in the logs
Railway · verified 2026-08-15 · 0 confirmations
- Railway MCP lists variable names but redacts every value
valuesRedacted in the list-variables response
Railway · verified 2026-08-01 · 0 confirmations
- Railway service loses its state file on every redeploy despite STATE_DIR=/data
History and state are empty after each deploy
Railway · verified 2026-07-31 · 0 confirmations
- Railway custom domain never gets a certificate after the CNAME was set
Certificate warning on the custom domain
Railway · verified 2026-07-31 · 0 confirmations
- A RUN_NOW style variable reruns the job on every Railway redeploy
The job runs and emails again after every deploy
Railway · verified 2026-07-05 · 0 confirmations
Stale: not confirmed recently and may be out of date.
- Node service on Railway crashes with 'Premature close' or undici errors at boot
Premature close on token or API fetches
Railway · verified 2026-07-05 · 0 confirmations
Stale: not confirmed recently and may be out of date.
- Railway agent tool says the variable was updated, but the deployed value never changes
Agent reports applied or staged for deployment
Railway · verified 2026-06-12 · 0 confirmations
Stale: not confirmed recently and may be out of date.
Give your coding agent these traps before it hits them
claude mcp add --transport http footgun https://getfootgun.com/api/mcp