@jonathanhefner I see. Sorry to waste your time. Just trying to figure out #39334 This is causing issues in production after a 6.0.3.1 upgrade. The fix is in place in master now. Hoping a 6.0.3.2 can be cut soon as its going to bite peeps who upgraded to 6.0.3.1 to fix this CVE.