Hello @weedor and @Marius,
Not quite sure how this didn’t come up in our tests. Apologies for the inconvenience caused.
This should be fixed in 1.2.1.8.1.