While our team continues troubleshooting this issue, one of our community members @agnieszkatracz has shared a workaround that seems to resolve the problem.
Please give this solution a try:
While our team continues troubleshooting this issue, one of our community members @agnieszkatracz has shared a workaround that seems to resolve the problem.
Please give this solution a try: