Unfortunately, this is a bug which can appear from time to time. Our technical team are aware of the issue, but do not currently have a recommended solution for it.

We are sorry that there is no troubleshooting we can currently recommend for this issue. If our technical team requires further information for further investigations, we will update this FAQ to request that reports be sent to our support team.