@ramscot
Our team has been made aware of this issue and we are working to have this issue resolved in an update in early February.
