This is happening for us as well. I will go through the help steps, but given that this is not an isolated incident (as it seemed to be when I first noticed it in December) - I think it is a QBO bug.
