We have a potential fix for this issue in v1.5.1 b4772 and we have also added some more info to the logs. Please give it a try and let us know if you continue to see this problem.
We have a potential fix for this issue in v1.5.1 b4772 and we have also added some more info to the logs. Please give it a try and let us know if you continue to see this problem.