a month ago
Project ID: 4419485f-4b00-4711-8ed5-bd475206b2c1
Service ID: 7ed40169-864b-4f90-9f8e-fcf744212558
Service: creator-os-bot
Environment: production
Issue:
My production runtime is online and healthy, but all deployment attempts are failing after the recent outage recovery.
Current state:
-
GitHub main contains latest commit:
bb0c530 — “Update creator dashboard referral labels”
-
Current active Railway deployment is stale:
0db8c858 — “Update favicon”
-
Auto-deploy is enabled
-
Latest commit never appears in Railway deployment history
-
“Deploy Latest Commit” fails / does nothing
-
“Redeploy” returns:
“Problem processing request”
-
API/manual deploy attempts also fail with unexpected client error
-
Runtime/logs continue functioning normally
What I already verified:
- Local git state is clean
- origin/main matches bb0c530
- GitHub push completed successfully
- Deployment issue appears isolated to Railway deployment triggering/state
This appears to be a platform-side deployment state issue for this service post-outage recovery.
Can Railway:
-
reset/fix the deployment state for this service
OR
-
manually force deployment of latest main commit bb0c530
@railway-support or @moderator Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 29 days ago