After updating the CMS to 3.3.2 some displays are showing a status of ‘Displays are out of date but have not yet checked in with the server’. I’ve tried restarting the players, but it doesn’t update. This is happening on Windows and Android players. Any ideas?
I do have navigate to layout actions, but only on one of my layouts. I noticed however that this layout has been deployed to all of my displays. I definitely didn’t schedule it that way. I’ve rolled back to 3.3.1 and that layout is still assigned to all of my displays even after purging.
If a Layout scheduled to a display has a Navigate to Layout webhook on it, then the layout with its matching layout code will also be downloaded to the display.
The bug above only happens if the layout targeted by the original layout refers back to the original layout, or targets another layout that refers back to the original (thus creating a circle).
I am not sure what is happening in your example above - if KEB Rotunda Left has an action on it pointing to KEB CP Main, then it looks right. If not, then we need to look for another reason KEB CP Main is on the display - perhaps a direct assignment?
The two layouts are unrelated. KEB Rotunda Left has no actions, it’s just has a playlist of images. It’s about as simple as you can get. I’ll keep looking around in case I missed something.
For KEB CP Main, it has quite a few webhooks that navigate to new layouts. Those layouts have webhooks that go back to Main. A separate control panel layout triggers the commands.
For KEB CP Main, it has quite a few webhooks that navigate to new layouts. Those layouts have webhooks that go back to Main.
It may be then that whatever has put KEB CP Main in the schedule (incorrectly or unexpectedly) is what triggered the above bug for you. Without looking its hard to say why you hit the issue, or why KEB CP Main is in required files where you do not expect it to be.
We have found the root cause of the above bug though and we’re pretty confident that its solved - we will release that in due course.
In the meantime i’d recommend you say on 3.3.1 and have updated the 3.3.2 release announcement with a note for users of interactive to do the same.