Hey everybody,
We fixed this issue internally and was scheduled to come as part of Hotfix 1 for Update 41. However, other critical issues took priority in the meanwhile. It’s possible that our next hotfix, scheduled for today, doesn’t include this fix since our priority at the moment is to get the other problems resolved as soon as possible. If that is the case, then it will be part of the second hotfix, also scheduled to come as soon as possible but after the critical hotfix.