@rjfowler If you are using an online version, it should be fixed. If you are using a desktop version, we are aware of this issue, and our development team is working on a resolution. We appreciate your patience.
