Users that should be auto-activated are set in a 'pending action' status.

Update timeline

1. resolved Jul 22, 2025, 06:00 PM UTC

   At 7/22/2025 11:30 AM PT, the Core Identity team became aware of an issue with authentication to our Core Platform service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, US Preview 1, EMEA Preview 2, US Preview 3, EMEA Cell 1. During this time, admins may notice some users that should be auto-activated stuck in 'Pending User Action' status. Our team is actively investigating this issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

2. resolved Jul 22, 2025, 07:25 PM UTC

   Okta has reproduced the issue and is currently working on a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.

3. resolved Jul 22, 2025, 07:54 PM UTC

   Okta has reproduced the auto-activation issue and is continuing to work toward a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.

4. resolved Jul 22, 2025, 08:37 PM UTC

   Okta has resolved the auto-activation issue and import functionality was fully restored at 1:37 PM PST. Additional root cause information will be available within 5 business days.

5. resolved Jul 30, 2025, 12:03 AM UTC

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On July 22nd, Okta triggered incident processes investigating issues affecting automatic user activation from API and Directory Imports across all production cells. Users were erroneously left in a pending state despite the update appearing as completed. Root Cause Summary: Okta Engineering determined that the root cause of the issue originated from an update deployed on 7:56 PM (PT) July 9th, which, due to a behavior change that mishandled user states, could result in some newly provisioned users being left in a pending state. Remediation Steps: Once the source of the issue was identified, Okta engineering rolled back changes at 12:11 PM (PT) on July 22nd. These actions successfully addressed the issue and restored normal operations by 1:29 PM (PT). Preventative Actions: To prevent future incidents, Okta is adding additional test cases and improving processes to better the resiliency of user auto provisioning processes. In addition, we are reviewing our internal processes to assimilate issues and expedite escalations to improve our time to resolve these types of issues. Total Duration: Total Duration (Minutes): 12 days 17 hrs 32min Actual Time: 7/9/2025 7:56:04PM - 7/22/2025 1:29:03PM Duration (# of minutes): Total Duration (Minutes): 17,280 mins