Actually there was a similar problem about a year ago, but it has been solved with a SW update:
Unless it is something trivial, I think @boldtrn or one of the developers may need to have a look at it, as I could not find a solution that can be applied by the user.
@Ted92 - have you already tried using different browser or the phone app?