We implemented a fix and are currently monitoring the result. The initial fix released on 07/25 was intended to resolve the issue, but once it was deployed, we identified that further adjustments were necessary. The second update is currently undergoing QA, and if it passes, it will be included in the next release on 8/20. We will update here if a fix can be expedited before 8/20.