Not true - it actually means that the “cached status” of the player in the CMS is deleted so that the next time the Player connects it recalculates from scratch.
I am certain that this was not the issue with your player - it was almost certainly the schedule issue we looked at in the other topic.
Here is the difference between “suggested” and “required”. We always suggest that the CMS/Player version is matched exactly - i.e. 1.8.0 with 1.8.0, 1.8.1 with 1.8.1 etc. However we do not introduce breaking changes in minor versions (unless we are talking alpha/beta). In other words it was not required to upgrade your players, but we suggest that you do.
I’ve not encountered this specific issue before - perhaps the content on Layout B was large and it took a little while to download? You can check the Display page to see the “status” of the Player, either tick, ! or x. I would expect the player to be a ! after a schedule change like the one you did, then switching to x while the player downloads the content, and then back to a tick.
The CMS isn’t mobile friendly - and we don’t claim that it is. It would be a non-trivial development project to get it to be mobile friendly and there are some parts of it that I don’t ever see as being mobile (i.e. the layout designer)
We’re happy to take suggestions - we have some thoughts on how we want the Layout designer to look. You can see them here: Layout Designer Timeline Improvements - #17 by dan
You’re welcome! 