Content changes should not need a technician visit

The problem with periodic-only syncing

Most digital signage players check in for new instructions on a fixed interval, often every fifteen to thirty minutes, to avoid hammering the network on a large fleet. That interval is fine for routine updates, but it is a genuine problem the moment you need a last-minute change to go live now: a corrected price on a menu board, a sponsor swap on an ad screen, or pulling a piece of content that should never have gone up.

Waiting for the next periodic check, or worse, driving to the location to reboot the screen, is not an acceptable answer for that kind of change.

How NoroCMS pushes changes out automatically

Whenever a playlist or schedule changes, NoroCMS resolves exactly which devices that change affects (the specific screen, or every screen in a targeted group) and automatically queues a lightweight refresh instruction for each one. Devices already check in for commands on a tight cadence as part of normal operation, so the instruction is typically picked up within about three minutes, without waiting for the next full periodic sync.

This is not a push notification service and does not depend on a screen keeping an open connection: the device is still the one reaching out on its own schedule, which is what keeps it working over unreliable cellular connections. The command is simply waiting for it the next time it checks in.

A manual override, for the rare case you need it right now

For the times when even a few minutes feels too long, an admin can click a per-device "refresh now" action from the dashboard to push the same instruction on demand. Most teams never need it, since the automatic push already covers the common case, but it is there as a fallback while troubleshooting or testing a newly paired screen.