clahey wrote:
We're actively working on fixing this. Sorry for the delay.
It's been about a week since this post. Any updates? Also, it would be interesting to know what the actual cause of the issue is and if there's anything we can do as a workaround.