Hi Maurice,

We became aware of this exact bug in 2.7.3, and I'm happy to report a fix has already been produced and was released yesterday as part of 2.7.4.

For reference TL-6647 was the issue used to track the bug.

Kind regards and best of luck with 2.7!

Sam