Jim M Posted June 15 Posted June 15 Unfortunately, this is not something which I can reproduce here. It may have been a temporary error but please let us know if you're able to reproduce it.
Nathan Explosion Posted June 15 Posted June 15 That error usually appears after an issue reaching the SQL database...and look at that:
David N. Posted June 15 Author Posted June 15 1 hour ago, Jim M said: Unfortunately, this is not something which I can reproduce here. It may have been a temporary error but please let us know if you're able to reproduce it. All I know is that it's been going on for a while. It happened multiple times on: 6/14 6/11 6/10 6/9 6/6 6/4 6/2 5/20 5/16 ... and that's as far as the logs go.
Jim M Posted June 15 Posted June 15 7 minutes ago, David N. said: All I know is that it's been going on for a while. It happened multiple times on: 6/14 6/11 6/10 6/9 6/6 6/4 6/2 5/20 5/16 ... and that's as far as the logs go. I have moved this to a ticket to be investigated by our Cloud team. Please watch your email for further correspondence. David N. 1
Recommended Posts