Thanks for reporting that @Retro808; here's the thing though, I'm still skeptical, and I'm betting that you were seeing the same issue as @lockian. Whatever the issue is, it appears to be sporadic, so you probably did see a legitimate issue. What was the exact error message? Any chance you can do some more testing to see if you can reproduce it again? If so, if you can enable debug logging that would be awesome.