a month ago
Most functions in Railway CLI are timing out consistently. This was happening yesterday too. I updated to 4.67.0, same issue still present.
Simple commands like -V and whoami work, railway link showed project/env selector steps then failed at the end. Status also fails ( see below).
$ railway -V
railway 4.67.0
$ railway whoami
Logged in as petereg
$ railway status
Failed to fetch: error decoding response body
Caused by:
0: error decoding response body
1: expected value at line 1 column 1
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Seems to have started working now? Was this an outage? Only thing I see on status site is a metrics outage.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Not sure, wouldn't it make sense to have the response in that case be a readable rate limit error rather than "error decoding response body" -- kind of has to be a bug now matter how you look at it?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
You're right — even if it was rate limiting (the most likely cause here, since cached local commands like -V and whoami kept working while the API-backed ones failed), surfacing it as "error decoding response body" is a bug. What's happening is the CLI receives a non-JSON response (e.g. a plain-text/HTML rate-limit or gateway page) and fails to decode it, instead of reading the status and showing a meaningful message.
We'll pass this to the CLI team to handle non-JSON responses gracefully and surface a readable rate-limit/error message. Thanks for flagging it, and glad it's working again in the meantime.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved jake • about 1 month ago