This should be resolved now. There was a fix deployed in recent daily release