@donovan_dmc said:
This looks like it should be an upstream issue, the same code that's triggering the issue here is present there
I have no idea where they are on deployments so the bad code may just not have been deployed yet

Oh, I completely skipped over that the setting needs to be off, this is in fact an upstream issue
I've put in a patch for us and will tell them about it

upstream issue?