Hi Christophe, Thanks for the report. This matches an issue already tracked internally. We’ll update the original thread once it’s fixed.