@UserCustomerGwen repoorted that they identified the issue. See link below.
Thanks @UserCustomerGwen.