Version: M54-Dev, build 8743.4.0, chromeos 54.0.2840.6

What steps will reproduce the problem?
(1) Enroll a device into a domain and Org. Unit which auto-launches a kiosk app.  (My case:  domain: crosprqa4.com;  OU: Engineering > Test;  App: Chrome Sign Builder)
(2) Reboot device, verify CSB auto-launches.  Let it run for a couple minutes.
(3) In Cpanel, move the device to another OU which also auto-launches the CSB app but has a different scheduling policy.  (my case:  OU: Operations > Facilities).

What is the expected output?
Normally CSB begins showing the new scheduling policy within 15 seconds.

What do you see instead?
The scheduling policy didn't change for nearly 20 minutes.

Granted, Cpanel has a disclaimer that a change may not be reflected for up to 24 hours, but the slow-down compared to my prior experience is bordering on "alarming".  (Not to mention my kiosk Sanity testing that
normally takes about 90 minutes took 5 hours.)

Another symptom which I suspect is related:  I moved the device into an OU on Friday (9/9) which contains some dummy cloud printers [DCP] (OU: Special Cases > Enterprise).  The device was unable to see any of the printers that day (approx. 4 hours elapsed time), even though other aspects of the OU were reflected, such as the wallpaper and app which gets auto-launched.  On Monday morning the DCP's were finally visible.