13 hours 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.
1 Replies
Status changed to Awaiting Railway Response Railway • about 13 hours ago
5 hours 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 • about 5 hours ago