Resolved -
Ticket opened - will be fixed in upcoming release
May 17, 04:40 UTC
Update -
We are continuing to work on a fix for this issue.
May 16, 15:29 UTC
Identified -
The issue has been identified and a fix is being implemented.
May 16, 15:29 UTC
Investigating -
We are currently investigating this issue.
May 16, 14:46 UTC