@JasonLord Thank you Jason for bringing this to our attention. I’ve just posted an update with a fix: