Timout updating variables
nikolandgraf
PROOP

2 months ago

When updating a variable via the CLI I get:

railway variables --service "xx"   --set "APP_VERSION=ABC"
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

When using the corresponding graphql request I get
curl --request POST \

--url https://backboard.railway.com/graphql/v2 \

--header 'Project-Access-Token: xx' \

--header 'Content-Type: application/json' \

--data '{"query":"mutation variableUpsert { variableUpsert(input: { projectId: \"yy\", environmentId: \"zz\", serviceId: \"pp\", name: \"APP_VERSION\", value: \"123\" }) }"}'

-> error code: 504

Solved

5 Replies

Railway
BOT

2 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

nikolandgraf
PROOP

2 months ago

Adding -skip-deploys seems to work in the CLI case. I guess this should still be treated as a bug

chandrika
EMPLOYEE

2 months ago

Hi there, glad you found a workaround but just confirming so we looks into the expected behavior on our end — this has been reproducible such that anytime you try to update variables, the CI fails with a 504 and adding the -skip-deploys flag deterministically fixes it?

Status changed to Awaiting User Response Railway • 2 months ago

chandrika

Hi there, glad you found a workaround but just confirming so we looks into the expected behavior on our end — this has been reproducible such that anytime you try to update variables, the CI fails with a 504 and adding the -skip-deploys flag deterministically fixes it?

nikolandgraf
PROOP

2 months ago

The CI always fails with this error:
Caused by: 0: error sending request for url (https://backboard.railway.com/graphql/v2) 1: operation timed out

Yes, skip-deploys fixes that

Status changed to Awaiting Railway Response Railway • about 2 months ago

brody
EMPLOYEE

2 months ago

For now, this is expected. Our gateway has a timeout, and if your deploy takes longer than our timeout, you will get a 504. So, using that flag is going to be the recommended approach.

Status changed to Awaiting User Response Railway • about 2 months ago

Status changed to Solved brody • about 2 months ago

Loading...