4 days ago
How can I resolve this?
Attachments
3 Replies
Status changed to Awaiting Railway Response Railway • 4 days ago
4 days ago
Hey, thanks for reaching out, there's nothing you can do on your side to resolve this. There is currently an ongoing incident and the team is actively working on a fix. You will be unblocked once the team has fixed the issue! Sorry for the trouble, you can track the incident here: https://status.railway.com/incident/QH8L8B3E
4 days ago
Hi Dev i am watching same issue in Status platform
Attachments
an hour ago
Sorry for the trouble getting deploys moving again. New deployments are being accepted on every plan.
Commits pushed while deploys were paused were not queued, so your service needs a manual deploy. Open the Command Palette (Cmd/Ctrl + K) and run Deploy Latest Commit. If that fails, reconnect GitHub in Account Settings. If you deploy from the CLI or CI, run railway logout then railway login, or create a new token, since earlier sessions and tokens were revoked. Full steps are in our recovery guide.
If the Limited Access banner is still there after a fresh attempt, reply with your project ID and the failed deployment ID and we'll look at it directly.
Status changed to Awaiting User Response Railway • about 1 hour ago
