Ok, we just deployed build 2.2.50 which should resolve this issue. Please confirm if that's the case.