@ProductTeam this is not a new issue, but we’re seeing more frequent reports of it since the last update to the add-on.