After a thorough investigation, our engineering team can confirm that this incident was isolated to a single customer's environment and was due to a change made within their Okta instance. Other environments should be unaffected by this issue.
We appreciate your patience while we investigated this issue. If you have any additional questions or concerns, please reach out to our support team.