873779ef-a0a8-4e05-a9d0-b5b8092788e9

have you pushed a commit or changed settings recently? There is a deployment overlap time on railway to prevent downtime, this can cause duplicated sessions with things like Discord bots

you can change the overlap time to 0, give me a sec to find the env variable

RAILWAYDEPLOYMENTOVERLAP_SECONDS

Didn't change any settings recently. Just pushed new changes in the codebase.

Will it go away if I just deploy again?

every time you make a change or a new deploy it will create a new environment, then will wait for an amount of seconds equal to the env variable I posted above, then remove the old environment

As I said in my first message, set the variable RAILWAYDEPLOYMENTOVERLAP_SECONDS to 0 in your service settings

I am not sure we are on the same page. Two deployments are running concurrently right now this moment. Replica is set to 1 and has always been. For some reason there is another replica running. I haven't deployed code in over hours. I guess I had a different timeline in mind when I said "recently"

I can see logs of the same thing its supposed to print twice. From two different replica / deployment id

!t

Hey @tensor8045, I raised the issue over to the support on-call. We will run an investigation as soon as we can.

Sure. Appreciate it.