Yup fix is in PR 
It will be in the next nightly and npm
3 Likes
@sebavan I can confirm that that fix worked in production. Thank you!
1 Like