Hi Will,

We haven't been able to repro this in house on 16.2 or later.

Since this problem is specific to 16.1 and we have 16.3 coming out in mid-November, we are going to encourage users to either upgrade to the current 16.2 build or to 16.3 once that is release.

Regards,

Jon