Apologies for the trouble. I believe this may be resolved in the issue below. This should be fixed in the next release of FusionAuth.
https://github.com/FusionAuth/fusionauth-issues/issues/1519
Please see the workaround mentioned in this issue and let us know if this resolves this issue for you.
Thanks,
Josh