I don't see any instances of the problem since August 28 (build 3016), so I agree this appears to have been solved.
I don't see any instances of the problem since August 28 (build 3016), so I agree this appears to have been solved.