Thanks for the bug report - this will be adressed in the next hotfix we produce.