Hey there! We've found the following might help you get unblocked faster:

• 🧵 Infinite applying changes

• 🧵 Stuck in Infinite Applying Changes

• 🧵 "Stuck in Applying Changes"

If you find the answer from one of these, please let us know by solving the thread!

Some how it got recovered. But still confused by the strategy of handling these kind of issues. There should be some kind of entry like "force removing a service" or so for user.

Sorry you ran into this!
I havent seen this too many times which is odd. If you run into it again, could you let us know while its happening and I can investigate it with live logs.

The issue began when I attempted to remove a deployment. Despite clicking "Remove Deployment" multiple times, after it changes to "Removing" for times, still nothing happened. The status refused to change, even though the deployment had stopped and all traffic was redirected to the new deployment. The UI still indicated that two deployments were active at the same time.

I decided to delete the service entirely and redeploy from scratch, hoping this would resolve the problem. However, it led to a disaster, as titled. Changes failed to apply because removing the deployment did not succeed. As a result, it wouldn't allow me to remove the service nor deploy the new service since an "action in progress" was ongoing, causing my project to freeze—no further actions could be taken until this was resolved.

I suggest implementing a feature that allows users to manually "force remove a deployment," as this capability is essential for situations like mine.

I have trusted your platform, but yesterday I felt powerless in this scenario. My only option was hoping that someone from support would notice my issue and manually change the status. Fortunately, the system eventually recognized the problem on its own and marked it as an "unknown error occurred", resolving what appeared to be an endless loop of applying changes.

Honestly, from my perspective, this situation should be addressed seriously moving forward.

Copy.
Would love to be honest thats not at all the end user experience we're aiming for. I've seen this issue where deleting/removing got suck once or twice before and its fairly inconsistent to reproduce so its been hard to debug on our end.
The goal of Railway is to make deployment and infrastructure frictionless and effortless so fixing these little rare and hard to reproduce bugs is extremely important.

That being said, I'll go ahead and ticket this so we can track the issue. I don't have a solid timeline with other things we're looking to fix/add but it is on our radar!

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!