@admin-5

Thanks for letting us know. This should now be corrected.

Thanks,
Josh
FusionAuth