Extended Maintenance Window

Update timeline

1. monitoring Jul 22, 2026, 03:14 PM UTC

   Please be advised that our scheduled maintenance is currently still ongoing, and the Okta Engineering teams are actively engaged. During this extended window, customers may experience errors when logging in to Okta Workflows. We appreciate your patience as our teams work to complete this operation as quickly and safely as possible. To understand how this might impact your organization and to view recommended workarounds, please review our detailed support article: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US . We will provide further updates in 30 minutes, or sooner, as more information becomes available.

2. monitoring Jul 22, 2026, 03:49 PM UTC

   Maintenance activity is still ongoing as we ensure the migration is completed safely and successfully. We will continue to share updates in 30 minutes or sooner, as they become available. In the meantime, please refer to the support article below for the latest guidance on workarounds and expected behaviors: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US

3. monitoring Jul 22, 2026, 04:19 PM UTC

   We are now observing stable system performance following the migration activities. Our engineering teams remain actively engaged in monitoring all services. Core workflows are recovering, and customers should see continued improvements. We will provide our next update in 30 minutes, or sooner if new information becomes available.

4. resolved Jul 22, 2026, 04:59 PM UTC

   After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved. Additional root cause information will be available within five business days.

5. identified Jul 23, 2026, 02:15 AM UTC

   The Workflows migration has extended beyond our anticipated completion and will now be completed at 4:00 PM UTC. We apologize for any inconvenience and will provide further updates as more information becomes available. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11

6. resolved Jul 29, 2026, 11:34 PM 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 our services to prevent future occurrences. We recognize that this maintenance ran beyond its originally communicated window and that our status updates during that extension did not keep customers informed in a timely way. We apologize for this; improving it is part of our preventative actions below. Detection and Impact On July 22, 2026, at 5:15 AM PDT, Okta Workflows in our North America region (FL1 cell) began experiencing issues that affected Workflows users across US Cells 1, 2, 3, 4, 6, 7, and 11. During this time, some workflow executions failed or ended prematurely, and users encountered errors loading the Workflows Console. Additionally, some app connections stopped working, requiring users to manually reauthenticate to restore functionality. Root Cause Summary The issue occurred during a planned system upgrade. A defect in a third-party vendor's software caused the upgrade to run significantly longer than expected. While migrating to a new datastore system, a communication failure between system components prevented the service from returning to its normal state within the expected window. During this period, the Workflows Console did not degrade gracefully when the underlying data store was unavailable; instead, it surfaced errors directly to users. In addition, app connections whose credentials could not be refreshed during the disruption were left in a failed state and were not automatically refreshed, which is why some errors continued after the upgrade completed, until the affected connection was reauthorized. Remediation Steps The third-party vendor confirmed the cluster stabilized at 8:34 AM PDT. Following stabilization, Okta Engineering recovered affected services to clear stale configuration caches. Any customers who experienced OAuth token refresh errors during this period were required to manually reauthorize any app connections. Full functionality was restored by 9:33 AM PDT. If you’re still affected: manually reauthorize the affected connection credentials in the Workflows Console (see KB: Okta Workflows: Cell Migration Expected Behaviors and Workarounds). Workflow executions that failed during the window can be re-run using your normal process; contact Okta Support if you’d like help identifying affected executions. Preventative Actions To prevent similar incidents from occurring, Okta has taken the following steps. We have enforced a fleet-wide hold on all further datastore engine migrations until our third-party vendor deploys a fix for the confirmed defect and confirms it is safe to proceed. We are also updating the Workflows Console to fail fast and recover automatically when infrastructure is temporarily unavailable, ensuring users see a reconnecting state rather than raw system errors. In parallel, we are adding direct automated monitoring and alerting for cluster-convergence failures to ensure faster detection during maintenance windows. Finally, we are improving how we communicate during maintenance that runs long, including a more timely status page and progress/completion updates. For questions about Workflows reliability or roadmap, your Okta account team can help. Total Duration Total Duration (Minutes): 258 minutes (4 hours and 18 minutes) Start Time: 5:15 AM PDT End Time: 9:33 AM PDT Duration (# of minutes): 258 minutes