#Instances still running

17 messages · Page 1 of 1 (latest)

steady lark
#

Hello everyone,

I'm reaching out for some help with a couple of issues I've been experiencing on the Railway platform.

First off, I've noticed that two instances of my environment are still running, even though I've deleted all my deployments. I thought maybe deleting all my projects might solve the issue, but it hasn't. The instances are still up and running.

Interestingly, these issues seem to be related to some deployment and building problems I had yesterday. Despite some initial crashes during deployment, it seems some instances have managed to run and continue doing so.

To add to the mix, I subscribed to a Teams membership yesterday and moved my project there. I thought maybe this new subscription could be causing the environment issues, so I decided to delete the team. However, not only did this not solve the problem, but I also lost my Teams membership in the process.

When I created a new team, I realized my membership didn't come back with it, which is a big problem for me.

So, I'm hoping someone here could offer some guidance. Why might the instances still be running, even though all deployments and projects have been deleted? How can I shut them down? And is there a way to get my Teams membership back after deleting the team?

Any help would be greatly appreciated!

sick dawnBOT
#

Project ID: N/A

gleaming wolfBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

steady lark
#

I don't have a project id, as i deleted it

tardy hull
#

Sounds like a phantom deployment

#

You'll have to wait until tomorrow when the team's back in office, and they'll delete it for you

torn siren
#

phantom deploy ^

sick dawnBOT
#

Flagging this thread. A team member will be with you shortly.

torpid valley
#

Having the same issue, arose yesterday as well. Deployed an instance and then a minute or so after it successfully built, it started up again. My Deploy Logs did not reflect this, only noticed from some notifications I had set up separately.

Attempted instance restart, rollback to previous instance, as well a fresh deployment but none were able to remove the phantom deployment.

project id: 0dc997ed-7908-49ff-89e4-b9c9797db190

dapper lodge
#

Can't really track it otherwise :S

foggy wedge
native haven
exotic grotto
native haven
#

the issue solved itself around an hour ago, and then with my most recent deployment (from railway cli - now removed) the cron job code was removed for me to test locally, yet it is still running 😦

#

like, the code to run the cron job was removed from my deployments yet it is still running