Ok, this error is not entirely helpful, but is generally shown when we have some performance issues, and I believe these have now largely been addressed. (From about 10 minutes prior to this post)
If you see the error again after you have read this (unexpected) please post here or send feedback.