@jason we found another possible cause of this issue and fixed it in v1.5.2 b4980. Please let us know if that addresses the issue on your end.
@jason we found another possible cause of this issue and fixed it in v1.5.2 b4980. Please let us know if that addresses the issue on your end.