Hello,
This was most likely caused by a bug for OIE Okta Orgs that was just recently fixed in the *.oktapreview.com environments as of release 2022.11.1
If you have a preview environment can you confirm if you still see this behavior. Production tenants *.okta.com will get the update later this month.
Thank You,