Sorry everyone, we have not been able to reproduce this issue in-house, but based on the logs collected from the original reports we saw an obvious bug which could have led to the behavior being observed here.
We’re in the process of collecting more information and are working to isolate the root cause and issue a fix.