Sorry about that!
I've been working with the platform crew for the past few weeks on getting this fix. Unfortunately this issue is not happening in our test environments, so when we implement a potential fix the only way to test it is to run a problem mode in live. We'll keep at it and hopefully nail down a fix soon.