Welcome to the community, @riozakies! We have a workaround in our support article that should solve this issue: