This has happened to me before a couple of times, it was on s3 and I just go to s1 and its fixed. By the time I come back, everything is back to normal so it works to re-log for me.

This has happened to me before a couple of times, it was on s3 and I just go to s1 and its fixed. By the time I come back, everything is back to normal so it works to re-log for me.