Darn. What’s going on? The error message appeared when I attempted to open the Dashboard. I started basic troubleshooting to determine the scope of the issue.
The most pressing question – Had my blog ceased to exist? I went to my blog URL (not through Dashboard), and all was OK.
The next question – was the error specific to the browser session? I opened another tab in the same browser window and received the error. I closed out of the browser window completely and re-opened Chrome. Hooray! my dashboard opened with no further error messages. A momentary hiccup.
If the issue had persisted, I would have done a few further checks before reaching out to tech support:
- Was the error browser specific? Attempt access through IE, Firefox, or Safari.
- Was the error across all methods of accessing WordPress? Attempt a post through the app on iPhone.
- Were other users experiencing the same issue? Google the error message.
I’ve worked on the insides of applications, partnering with developers to roll-out new functionality and troubleshoot bugs. Dealing with a system outage is an exercise of communication, coordination, and sometimes luck. I am not often on the customer side of the tech support equation. Tonight was a reminder that the person experiencing an error message just wants stuff to work the way it always works and does not care about server maintenance or load balancing or the stars being out of alignment.
I just want to be able to post happy pictures like these of the kids’ new sunhats and a beautiful blue day.