How often does this happen? Does re-triggering the workflow fix this?

I have re-run the job 4 times, and each one has failed. The fourth was just now at 5:22pm CST today. The first one was 1 hour before that at ~4:20pm CST.

Thanks for the info; we're gonna have a look at this.

Still seeing the issue today.
npm i -g @railway/cli

railway variables --service api --set "ENVIRONMENT=production"

shell: /usr/bin/bash -e {0}

env:

SERVICE_DIR: ./src/services

RAILWAY_TOKEN: ***

npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead

npm warn deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exhorbitant rates) by contacting i@izs.me

added 17 packages in 4s

3 packages are looking for funding

run npm fund for details

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

Error: Process completed with exit code 1.

I removed the call for setting the environment variable and now just using the railway UI to set the value. The process now works.