2 months ago
Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)
Caused by:
0: error sending request for url (https://backboard.railway.com/graphql/v2)
1: operation timed out
Maybe this happens if I have deployed too frequently, or maybe it's random. Deploy mostly works, but fails sometimes. When it fails, it keeps failing for a while.
Pinned Solution
2 months ago
There's a 35s gateway for the railway up command. If your deploy takes just a bit too long, it times out which would explain why it works sometimes but not others.
I've seen a related thread where the --skip-deploys flag with railway up was used as a workaround, could you try that?
5 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hey I’d be happy to look at it for ya.
2 months ago
Hey, this usually happens when you are deploying a really big repo.
I suggest you try optimizing your repo size, you can do so by including unwanted files/folders in the .gitignore file, removing build artifacts...
2 months ago
I use an approach where I specify what is included rather than what is ignored.
I push vars, schema and code. Most of the time it works, and hasnt failed in the last 7 or so pushes, so I expect it's either a rate limit or traffic-dependent
frontenddevguy
I use an approach where I specify what is included rather than what is ignored. I push vars, schema and code. Most of the time it works, and hasnt failed in the last 7 or so pushes, so I expect it's either a rate limit or traffic-dependent
2 months ago
There's a 35s gateway for the railway up command. If your deploy takes just a bit too long, it times out which would explain why it works sometimes but not others.
I've seen a related thread where the --skip-deploys flag with railway up was used as a workaround, could you try that?
2 months ago
It hasnt happened again, so I will consider it an edge-case
Status changed to Solved medim • about 1 month ago