You were right to be concerned—you did have two active deployments running simultaneously, not a UI display issue. That's why it kept reappearing even after you disabled automated deployments and crash restarts.

What likely happened is that both deployments were independently respawning when they crashed or when the system tried to clean them up, which is why removing restart limits and disabling automations didn't help—each deployment had its own lifecycle and crash protection.

We've manually removed the old deployment from our end, so you should now have just the one active deployment. Can you verify in your dashboard that you're only seeing a single deployment now?

Going forward: If you see an old deployment reappear after a redeploy or major change, it's usually safe to hit the "Remove" button directly on the deployment card. But if it happens again and won't go away, reach out—there might be a webhook or automated trigger re-creating it that we'd need to investigate.

Thanks so much for your reply and your action. I checked the dashboard, sadly the second deployment was still active and when I deleted again it came back. I don't want to waste too much time of yours and mine, and the LLMs were in agreement that this service was now "cursed" so I created a new one and moved the service there - mine is a hobby project so I can live with a few mins of downtime (domain changes).

And by the way, kudos to you guys for building such a great system that this is possible to do within 10 mins.

Two feedback from that:

1) I didn't need to have downtime but had to because I cannot move domains between two services (I cannot add the same domain to another service if it's already active, no option to "move" that I could find). [I didn't want to fiddle with cloudflare too much]

2) I need to delete a service to be able to move the attached storage (or I couldn't find the option to move if there is one), which also creates some downtime (or backup wizardry, which I now built - gotta love the coding agents).

And it's been 10 mins or so since I started to delete the cursed service, it still isn't deleted (maybe this is normal), FYI. [Edit: the deletion also failed, so definitely something wrong - could you actually delete it please? I don't know if it's still up or not]

Many thanks for your help again, things are OK for me but I think you have a bug somewhere there.

No I agree, this does indeed smell like a bug but since it's the holiday period. It's a bit difficult to get down to the bottom of where it might lie. As long as we are good for now, I think we can mark this as solved!

I just see this annoying thing when the old service is not deleted, could you please delete the old service (marked for deletion) manually? It keeps failing on my end however many times I try.

I have forced killed the deployment, you may now delete the service.

thank you, all done.