During the updating of a deployment of my telegram bot, I noticed that the build was failing on the bot with a nixpacks error. I didn't know what the error was, so I tried to redeploy, which failed.

I then removed the new deployment and attempted to redeploy the old instance, which was the one I wanted to replace, and which had already been running. That didn't work either, so I turned off private networking thinking that was the issue.

This worked and the deployment succeeded, but afterwards, I realised that the telegram bot was responding twice to every message I sent to it. Checking the logs, I found out that there were 2 instances of the bot running, despite railway dashboard showing me that there was only 1 deployment live.

I then removed the service entirely and the bot was still responding to my commands on telegram, which leads me to think that there is an instance of the bot running on the server, which has somehow gone rogue and failed to shutdown when I redeployed. Is it possible for a staff member to manually kill the runtime for me?