13 days ago
We are creating new environments in Github Action via CLI by cloning existing staging environment:
railway environment new "$ENV_NAME" -d staging -v <redacted> SKIP=ME
The command errors out with
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
This has been happening on Wednesday, it was fine on Thursday but now it's timing out again (Friday).
5 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
12 days ago
The timeout is on our side, not your CLI command or flags. Duplicating your staging environment is intermittently taking longer than the CLI's request window allows, so it reports a timeout reaching our API even though the duplication often finishes on our end a little later. That's also why a retry can come back with "an environment with that name already exists" - the first attempt actually created it despite the timeout. Before retrying, check whether the new environment was created; if it's there, the clone succeeded.
I'll forward this up to our CLI team to see if they can see why this is happening as well
Status changed to Awaiting User Response Railway • 12 days ago
12 days ago
Yes, I can confirm that the environment is always created successfully but it's also always empty. This breaks our pipeline on 2 fronts
- it marks 1st run of pipeline as failed (not great, not terrible) but
- rerun of the pipeline also fails because the environment exists (we check and we don't create a new one) but without any services, meaning that any deployment will fail, regardless how many times we retry the pipeline.
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
If the command doesn't time out, all services are duplicated successfully. If it does, they are not. The timeouts and failed duplications started happening on Wednesday, it worked before for many months.
12 days ago
Temporary workaround is to manually sync empty environment from staging to create empty services, then re-run the pipeline.
12 days ago
Hey! just wanted you to know I escalated this up to our team to look into.
We'll follow up when we have a resolution. Sorry about the impact in the meantime.
Status changed to Awaiting User Response Railway • 12 days ago