@cookalistair I’m aware of the issue, we’ll push a fix very soon, still trying to reproduce and locate the cause, probably a mistake somewhere