Further findings… it looks like there is some built in logic either server side or client side to not correct the time if it’s within a defined tolerance…
If I’m right, that’s annoying, as that tolerance allows for (at least) a 20 second drift!
Explain a lot of my frustrations over the years - I believed my daily time sync call wasn’t working - but it probably was, just that the logic rendered it useless.
It’s only now that I’ve been given the code to trick the Core into taking on a totally wildly ‘out’ time, that I’ve been able to test what’s going on.
@jvanier @marekparticle - am I right in what I think I’ve found ?