@Dr.Ko and @friedkiwi it’s likely related to the change in the v1.104.5:
but it should be fixed in the next versions