Hey @caseyghancock,
I was jumping in to announce the fix for this issue shipped in 4.6.24.1, but seems like you already took advantage of this 🙂
Thanks so much for the patience while we worked on a solution for this issue. I’m closing out the thread but please don’t hesitate to open a new one if you still need help.
Best,
Nico