I see that error all the time so it's probably not related to the meltdown. Usually trying a different browser and/or signing out and signing back in fixes it for me.