@misty We’ve fixed this in the current internal build. So should work in the next release.