Hi Kevin, as Bryan mentioned, this is a known issue, and we have a fix planned for the upcoming hotfix.