Old deployments keep showing up
I sometimes want to take my service down to do some maintenance. I just go to my most recent deployment and remove it.
But then it shows me an old failed deployment. Like months old deployment. See image below. When I try removing it, another one shows up, even older and it never stops
34849d22-d685-4e73-8858-fbd4fe42ea65
14 Replies
Project ID:
34849d22-d685-4e73-8858-fbd4fe42ea65Still happening
service?
any of api/worker/cloud-processor, but I have some active deployments at the moment. I can record a video if that helps, but can't really leave a service in the broken state for long
does that failed deployment show up in the history portion?
Well, that’s a good question, the failed deployments are 18 months + old, so I’m not gonna bother scrolling to verify 😅
Maybe I can use the graphql api to check if there is a query for it?
I think that's a little overkill, simply look at the UI next time that shows up
Alright, actually scrolling through deployments was quite and yes failed deployments are still showing.
- First image is "api" service. I already removed a bunch manually so no surprise it's very few left.
- Right image is "cloud-processor", I was kinda tired to do the same as what I did on API, so there is a lot more and I didn't included everything, there are dozens more failed deployments.
- I would expect the same on the "worker" service
okay so these are in the history, why does it matter if the history is showing you your history?
Because when I removed my active deployment, the last failed deployment is "promoted" at the top of the list.
Instead of showing the empty placeholder "There is no active deployment for this service." I'm getting some months old failed deployment
these highly cropped screenshots aren't doing any favors 🫤
fair, will take a video next time I'm removing my deployment
here you go
gotcha
I'll create a ticket for this and get back to when / if this behaviour is changed