I forgot to change the Message Server setting to explicit IP. I’ve tried that and verified everything you said. Every machine use 5.1.60. Still the same behavior. Here are the screenshots
I have to say that this observation is not always true, but the task state changes are indeed the major (if not all) part of the update problem I’ve experienced. I’m of course not an expert on the working of SambaPOS, but it seems almost like the signal to update the screen arrived faster than the task update itself, therefore the complete state got “stuck”.