Adding that our issue appears to be very similar to this issue from May 3:
Which doesn’t appear to be resolved.