Hello @Chris,
This is the same issue. We’re working on a fix, and it will be resolved in the next update.