Thanks for letting us know about the issue (and sorry for the late reply..! ) but we have been looking into this problem. It may be a version update issue that we aren't able to recreate, but hopefully stability improvements in upcoming versions will make this sort of problem less likely!