UPDATE - it seems the fix was a part of another solved challenge, so this issue exists in 11.0.3 but already fixed in the closest release but without the separate ticket.
