a month ago
Hi Railway team,
I’m having an issue with a GitHub-backed service that can no longer deploy.
Service/repo details:
Service: opencreator-agent
Repo: OpenCreator-ai/opencreator-agent
Branch: develop
Environment: Dev
Domain before the issue: https://agent-dev.opencreator.io
What happened:
The Railway service initially started showing a 404 / unavailable state.
I pushed new commits to the GitHub repo, but Railway did not create new deployments.
I tried reconnecting GitHub and pushing additional empty commits to trigger deployment, but no deployment was created.
I also tried redeploying/restarting from the Railway side, but the service still did not recover.
I then removed the service/deployments while trying to fix it.
Now the service is offline and cannot be redeployed. The dashboard shows: “There is no active deployment for this service. Deploy the repo OpenCreator-ai/opencreator-agent”, but redeploying the repo does not work.
Current state:
The service appears offline.
Deployment history only shows removed deployments.
No active deployment exists.
New GitHub pushes are not triggering deployments.
Could you please help check whether the GitHub integration or deployment state for this service is stuck/corrupted, and help restore the ability to deploy this repo to the service?
I’ve attached screenshots showing the current service state and the technical help form.
Thanks!
2 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
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.
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 • 30 days ago