We pushed a fix last week but have heard from one community about this again. Happy to review if this is still an issue.