Hello @Nitti, this was an unintended change and should be addressed in an upcoming hotfix, apologies for the situation.