2.2.41

Reply to this note

Please Login to reply.

Discussion

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

Thank you. All good