The issue has been fixed, and we are currently monitoring the result.
We have identified and are continuing to work on a fix for this incident.
