Yes, I’ve marked on the email reply to you, or you may have it here:
I reproduce the error at 2017-07-14, (UTC+8) 00:31(am), and generate the log in roon core with the support ID, it take quite long and finished at (UTC+8) 00:38.
To bring all of you up to speed, we believe that we’ve identified the issue and a fix has been set into place which is pending our next build release. When it goes live please update and let us know how it goes.