Sorry about that, fixed in next hotfix— Steve Sinclair (@sj_sinclair) March 25, 2017
Sorry about that, fixed in next hotfix