I am trying to see if I can track down who may have actually put in the change that corrected this issue, at least when I tested on our latest internal build. I had to artificially set up the issue that was occurring normally for everyone else in this post, so I cannot be completely sure that it has been corrected until we release a version containing the fix that you can try.
If I am unable to determine the precise fix, 4.14 should include the changes that allowed my test to work successfully. We have already branched that version, and the first preview should be released soon.