3 months ago
Randomly started getting:
Failed to get deploy status: <query>:0:0: Problem processing requestwhen doing railway up. Is something down? It does actually fire off a deployment, but something must be reporting badly to the CLI so it fails
Have the following in my github actions:
Run for i in {1..2}; do
for i in {1..2}; do
echo "Attempt $i: Deploying App"
if railway up --service=***; then
echo "✅ Deployment for App successful on attempt $i"
exit 0
fi
echo "❌ Attempt $i failed"
sleep 5
done
echo "❌ All attempts failed"
exit 1
shell: /usr/bin/bash -e {0}
env:
RAILWAY_DASHING_SERVICE: ***
RAILWAY_TOKEN: ***
Attempt 1: Deploying App
Indexing...
Uploading...
Build Logs: https://railway.com/project/xxxxxxxx/service/***?id=yyyyyyy&
CI mode enabled
Failed to get deploy status: <query>:0:0: Problem processing request
❌ Attempt 1 failed
Attempt 2: Deploying App
....Tried a few times but always the same.
6 Replies
3 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!
3 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
3 months ago
Thanks.
This is failing on the CLI version 4.11.2 so tried it also on 4.11.0 but both are failing so imagine its something with the response.
3 months ago
Apologies for the wait here. We've just merged a fix for this. Could you try again?
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
✅ The ticket Authorization Issue Detected has been marked as completed.
3 months ago
Thanks, all working now
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved oligirling • 3 months ago