Okay, I missed your other report of this issue @thigg, which we already had an internal bug for. Hence I’ll close this one. Thanks @abranson for directing me.
For anyone else hitting this issue, please add additional discussion to @thigg’s slightly more detailed report here: