Okta experienced a major incident on July 7, 2026 affecting Workflows, lasting 19d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 07, 2026, 08:15 PM UTC
At 7/7/2026 12:40 PM PT, the Workflows Automation and Extensibility team became aware of an issue with to our service affecting customers in US Cell 14. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next , or sooner if additional information becomes available. Affected cells: okta.com:14
- investigating Jul 07, 2026, 08:50 PM UTC
Okta engineering has an identified an issue affecting Okta Workflows and are currently taking steps to remediate. Customers may see 500 errors or timeouts in the Okta Workflows console, API endpoints, and inbound webhooks. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.
- resolved Jul 07, 2026, 09:03 PM UTC
The issue with Okta Workflows has been resolved. All Workflows are now processing normally. A root cause analysis (RCA) will be posted here within five business days. We apologize for any inconvenience this may have caused.
- resolved Jul 15, 2026, 03:22 PM UTC
We sincerely apologize for any impact this incident may have caused to you, your business, or 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 7th, 2026, at 1:01 PM PDT, Okta internal monitoring and customer reports alerted our team to issues with users accessing Workflows on the Okta cell OK14 in North America. During this period, customers on FL14 may have experienced HTTP 500, 503, or 504 Gateway Timeout errors when navigating to Workflows from the admin portal or attempting to log in to the Workflows Console via SSO. Existing sessions may have errored out intermittently. Scheduled and on-demand workflows, inline hooks, and webhooks may have experienced errors and timeouts. Additionally, in-flight executions experienced timeouts. Root Cause Summary: This incident occurred during the planned deployment of release 2027.07.0 to the FL14 cell. In the course of the deployment process, a service pod responsible for executing schema updates was terminated prematurely. This early termination led to unexpected, long-lived database connections, which ultimately caused connection exhaustion on the cell's primary database. Remediation Steps: Upon receiving alerts and customer reports, the team began diagnostics at 12:44 PM PDT. By 1:30 PM PDT, they isolated and removed the service pod performing schema updates. This allowed the database connections to clear, restoring full service by 1:45 PM PDT. Preventative Actions: To prevent future occurrences, Okta is committed to strengthening our infrastructure stability and enhancing our monitoring capabilities. We are currently implementing strategic improvements to our deployment processes and alerting systems to ensure faster detection, response and greater resilience across our services. Total Duration: 67 minutes