Answer
Before assuming it's a server-side performance issue, check the client machine's local application cache — clearing a stale local online-app cache has resolved this specific error for some users, which points to a client-side caching problem rather than something server capacity alone would fix.