AnnetteB6, thanks for finally posting on this discussion (i had asked for this days ago). As others have stated this should not be a difficult fix. It was not broken last year and for me it started after the 3/3/22 update. Why is it this can't be fixed right away?
Again, thanks and appreciate anything that can be done by TT to get this fix made and deployed ASAP.
And BTW your workaround is not reasonable since have 250 false errors from this.
