I’m sorry to say, but with 1.6.1 I had the same issue pop up yesterday, after a longer period with no issues.