The issue was resolved for us so I’m guessing the fix was implemented @Alan . I’ll go ahead and close this for now. Thanks!