13 days ago
Hello Railway team,
We have a deployment in our production environment that remains marked as ACTIVE even after multiple removal attempts.
The dashboard returns:
Problem processing request
We also tried removing it through the API/CLI without obtaining a confirmed successful result.
Automatic deployments are disabled, and the GitHub branch has been disconnected.
We have successfully restored our application's availability through a separate deployment, but the old deployment still appears as ACTIVE.
We need to confirm whether that old container is actually running before performing a scheduled database migration.
Could Railway staff investigate the deployment state and help us safely terminate the old instance?
We can provide project and deployment identifiers privately if needed.
Thank you.
4 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
We found the deployment. Our records still list its instance as running, and the removal requests from today, including yours, are failing on our side. That failure is what's behind the "Problem processing request" error. It isn't caused by your settings, the disconnected branch, or the way you tried to remove it.
Because removal hasn't completed, we can't yet confirm whether the old container has actually stopped. Please treat it as possibly still running when you plan your database migration.
You don't need to send us the project or deployment identifiers. We were able to find the deployment from your account.
Status changed to Awaiting User Response Railway • 13 days ago
angelo-railway
We found the deployment. Our records still list its instance as running, and the removal requests from today, including yours, are failing on our side. That failure is what's behind the "Problem processing request" error. It isn't caused by your settings, the disconnected branch, or the way you tried to remove it. Because removal hasn't completed, we can't yet confirm whether the old container has actually stopped. Please treat it as possibly still running when you plan your database migration. You don't need to send us the project or deployment identifiers. We were able to find the deployment from your account.
13 days ago
Hello Angelo,
Thank you for investigating the issue and confirming that the deployment removal failure is occurring on Railway's side.
We appreciate your assistance.
Given that the old deployment may still be running, we would like to understand how we should proceed.
Should we wait for Railway to resolve the underlying issue on your side, or would it be possible to request a manual intervention from your engineering team?
Specifically, would your team be able to:
- Safely terminate the old deployment without affecting our current working deployment.
- Correct the old deployment's ACTIVE status once its termination has been confirmed.
- Verify and confirm that no container or process associated with the old deployment remains running.
Our main concern is ensuring that the old instance can no longer access our production MongoDB database before we proceed with our scheduled migration.
If these actions require an infrastructure fix rather than manual intervention, could you please let us know whether the issue is already being investigated and what the recommended next steps would be?
We would like to keep our current production application running without interruption.
Thank you again for your help.
Status changed to Awaiting Railway Response Railway • 13 days ago
12 days ago
We've cleared the stale record for the old deployment, so it should no longer show as active, and your current deployment doesn't need a redeploy.
Status changed to Awaiting User Response Railway • 12 days ago
12 days ago
Hi guys,
I wanted to confirm that the issue has been fully resolved.
The stale deployment is no longer active, and we were able to successfully complete our production migration and deploy the latest version of our application.
Everything is now running correctly, including our production database connectivity and custom domain.
Thank you very much to Brody, Angelo, and the entire Railway team for your assistance, especially over the weekend.
We really appreciate your support and the effort you put into resolving this issue.
No further action is required on our end, and this ticket can be closed.
Thanks again!
Best regards,
Lionel
Status changed to Awaiting Railway Response Railway • 12 days ago
Status changed to Solved Railway • 12 days ago