Unable to delete ghost service
fredovecino
HOBBYOP

3 months ago

Hi,

I have been trying for quite a while to delete a service in my project but no matter what I do the service is still there.

What did I do:

I deleted the service dq-frontend

Renamed another service to dq-frontend

Failed to rename because the name exists

What I have tried:

It used to show up in the canvas so I deleted it from there multiple times until it stopped showing.

I navigated to the settings > danger and delete it from there multiple times but it always stays there.

Project ID: 55ed39b2-1e97-4d6d-841f-67bcbc646fa5

Can you guys help me deleting this service for good?

Solved$10 Bounty

9 Replies

fredovecino
HOBBYOP

3 months ago

I want to rename my service from dq-frontend-pub to dq-frontend

rail03.png

rail02.png

rail01.png


3 months ago

Please link the service.


fredovecino
HOBBYOP

3 months ago

I can't link the one I want to delete, I can only link the one I want to keep


3 months ago

A service named "da-frontend" already exists in that project.


fredovecino
HOBBYOP

3 months ago

That is the ghost service, I can't see it in the canvas nor delete it. Can you delete it?


3 months ago

It's not a ghost service, it's in your staging environment, if you want to bring it to production use the sync feature.

image.png

Attachments


fredovecino
HOBBYOP

3 months ago

Hmm that is some weird behaviour because I should be able to rename my production service dq-frontend-pub to dq-frontend and I can't. When I try to sync it's just creating a new service but I already have one there for that purpose.

Not sure how that happened but with your instructions now I know how to fix it.

Thanks


3 months ago

The names of different services need to be unique across all environments. To carry across the same name, you must use the sync feature. That way, it's the same service across the environments, just different service instances.


avecino
PRO

3 months ago

Ok thanks for clearing that up for me.


Status changed to Solved sam-a 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...