@PattieMoore Thank you for reporting this issue.
Another user reported this issue last week and we are working to have this issue resolved in an update in early February.
