Hiya @jkyser ,

Hmmm. What version of FusionAuth are you running?

It looks like this is a known issue that was fixed in release 1.46.0.