Hi Martin,
I tried to recreate the issue in a clean version of public 4.11.2 and I was unsuccessful as well. It truly might have already been fixed. Thanks for your help. I’ll let you know if it so happens that the problem still occurs for us when we upgrade our main branch to 4.11.2 in the future.
Kind regards,
Marcin