Hey @dmw33
We’re aware of this one and a fix for it is being developed internally. Thank you for the feedback.