This issue has been resolved!
We have implemented a fix for this issue and are currently monitoring the result.