Hi
We have four developers who create NSQ's from our clients 16.4 , however when two of the developers save anything in the NSQ the scheduler on the server will be stopped with the following message on the logs
Message Scheduler stopped
I can understand this if we were changing the Schedule in the NSQ and then saving but just saving the NSQ should not behave like this? Why would it be doing this for Two developers and the other two developers can just SAVE when they like without affecting the scheduler on the server?
Seems strange behaviour to me but hopefully somebody can shed some light on it for us?
