I had that error until V5.0.28 and not once since. We are now upgrading to V5.0.29.