Just confirmed - there was a known issue that was recently fixed. It will go out with our December Release (~ 12/16).
View solution in original post
