HI @rastallp et al,
I don’t have any update on this, and my last post remains much of the same.
The team is still looking into this and if I hear anything I’ll update this thread. If anyone has reached out to support to log a case with them, you’ll also receive a follow up email once resolved. I would recommend calling to log a case with the team if you haven’t already as this helps boost the case count the issue has, the more cases tagged against an issue the higher priority it becomes.
To set expectations, I don’t have an ETA to share on when this will be resolved, and I probably wont have any news until this is resolved: you’ll most likely see the issue resolved in the app yourself before I reply to this thread once it is fixed.