I am running 18.104.22.1686 in several environments (Dev, Test, Prod) When I try to lower the system queue to 0 so that no new jobs launch, my entry is overwritten and goes back to the previous set number. Even if I set it to 1 it goes back to the previous number. This is happening on all 3 masters, so I don't think it is a quirk with my install. In earlier versions of 5.3.1 I was able to do this.
Has anyone else experienced this? In dev, I stopped Tidal and snuck into the database and edited the limit (definitely not supported by Tidal, but wanted to see what would happen.) My zero setting stayed 0.
I haven't called Tidal Support about this yet...wondering if it is just me.