Hello, I encountered such a problem, in the dashboard I have disabled all deployments, but the bot continues to work, if you add a new deployment, then it works in parallel with the old deployment of the bot, is it possible to somehow find this active code and disable it or is it possible to completely disable all options launched earlier, it will not be displayed in the list, everything that is all deleted, I already tried and disabled the project from the repository from the github and completely deleted the project, nothing helps
#Нow to disable all deploys or find which of the deploys is still working
1 messages · Page 1 of 1 (latest)
Project ID: e81e13b1-1b73-4e4e-9994-f4df02472333
You can remove the deployment itself. No need to delete the entire service. Reactivating a previous deployment or pushing changes can also temporarily disable the trigger.
⚠️ experimental feature
you're absolutely positive you're not running the bot somewhere else besides railway?
like accidentally in the background on your computer
yes, the bot is running only here on railway)
okay, please link your account
I connected)
thank you
Is it possible to fix this somehow or will I have to delete my account, or will this not help?)
Flagging this thread. A team member will be with you shortly.
ok thanks, I'll be waiting)
I apologize for writing again, I would like to know if it will be possible to do something today?)
If it’s possible to disable all versions of the bot so that I can enable the new version, now when you enable the new version, 2 options work at once, I tried to disable the github from the account and completely deleted the project, but it didn’t help, here’s the ID of the old project 548e4234-0783-4ae9-9bef-fd491030d8b8 , I think the old one works on it version
this is caused by a phantom container, no amount of deleting projects will help, I've asked the team. if you can't wait and want a solution this instance, regen your bot token and the bot that's currently running will eventually fail and be kicked offline
well, thanks for the idea), I will wait of course and the answer from the team))
If I was you, id regen my bot token anyway
ok
unfortunately this method did not help, I updated both the tmi token and the id client, but the old bot continues to work(
@old trellis sorry for the ping
that's funny
hello, I still don’t know what else to do to disable the old version of the bot, it still works, even changing tokens and id didn’t help, it’s very strange, this is the first time I’ve encountered this, before that everything worked fine for a couple of months.
I updated both the tmi token and the id client, but the old bot continues to work(
Did you remove/invalidate the existing token? What bot is this?
bot from twitch, I updated the id client at twitch itself, according to the idea, the old token should become inactive and the bot should turn off, but this did not happen, if I add this new id to railway variables, both versions of the bot and the old one that I cannot disable will work and it's new.
damn twitch you letting people use invalid tokens
usually if the token is not the right one, it immediately gives an error when connecting, but it turns out that both the old one and the new one work, or the twitch saves the client id and tmi token until it is disconnected from it, even if a completely new one is created, very strange
Update on this. We were able to find the phantom container that wasn't properly terminated and stopped it. We're looking into why this one didn't get cleaned up properly