Hi
Has there been any further action on this issue? We are getting the same error (also randomly)