Okta experienced a major incident on October 1, 2026 affecting Workflows, lasting 10h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2026, 01:17 PM UTC
On October 01, 2026, at 6:17 AM PT, we're investigating an issue with Okta Workflows where some automated event hook triggers aren't executing as expected. Our engineering team is actively analyzing system logs and working on root-cause remediation. We will provide an update within 30 minutes or as soon as additional 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
- identified Oct 01, 2026, 03:17 PM UTC
Mitigation steps have been implemented to address delivery and execution delays affecting automated event hook triggers in Okta Workflows. System telemetry indicates that event delivery is recovering and that backlogged automated workflows are beginning to process. We are actively monitoring performance to ensure full stability. A follow-up update will be provided within 15 minutes.
- monitoring Oct 01, 2026, 03:50 PM UTC
System metrics continue to demonstrate sustained recovery following the applied mitigation. New events are being processed successfully, and backlogged events continue to be processed with no recurring errors, consistent with initial customer feedback. We are maintaining active monitoring to ensure ongoing stability. We will provide a final update in 30 minutes or upon formal resolution.
- monitoring Oct 01, 2026, 04:20 PM UTC
Okta Workflows performance remains stable, and remaining backlogged events continue to be processed. To ensure sustained system health across all tenants, engineering will maintain active observation. We will share the next update in 60 minutes or as soon as service stabilization is fully confirmed.
- monitoring Oct 01, 2026, 05:45 PM UTC
We have confirmed recovery across several Okta cells, where event hook processing has normalized, and queue backlogs have cleared. Engineering is continuing to track processing metrics across all remaining cells as backlogs normalize. We remain in an extended monitoring phase to ensure sustained system stability across all cells before declaring full resolution. Our next update will be provided in 60 minutes or upon formal closure of the incident.
- monitoring Oct 01, 2026, 07:38 PM UTC
We have remediated the root cause affecting automated event hook delivery in Okta Workflows, and the majority of cells have fully recovered. A subset of cells continues to process a backlog of queued events; based on current processing rates, this may take up to 12 hours to complete. We remain in an extended monitoring phase while this backlog clears, and we will provide a further update as the situation progresses.
- resolved Oct 01, 2026, 11:59 PM UTC
Following a period of active monitoring, we can confirm that this incident has been fully resolved. Automated event hook execution and queue delivery are operating normally. Additional root cause details will be provided in a formal report within five business days.
- resolved Oct 09, 2026, 03:44 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 October 1st, 2026, at 6:55 AM PDT, Okta customer reports alerted our team of workflow lag issues for US Cells OK6, OK7, OK8, OK9, and OK11, as well as Okta Preview Cell OP1. During this incident, customers using Okta event hooks experienced delays receiving subscribed events. Workflows triggered by Okta webhooks would have also executed with delays or become non-responsive. In US East Okta Cell 11, a subset of events was dropped entirely, and the webhook delivery failure logs do not appear in the system logs. Root Cause Summary: During our transition to a new internal event delivery system, Okta experienced an issue where retried, consistently failing event hooks deliveries blocked the processing of the queue. Once the primary queue reached max retry events, the system was unable to process additional messages from the queue, causing widespread delivery delays. Additionally, because the queue did not throw error alerts when it became saturated, our standard monitoring did not immediately flag the issue, allowing the backlog to persist until customers noticed gaps in their expected data. A small number of customers were affected by a migration misconfiguration stemming from an unrelated prior incident. This configuration error caused the new delivery system to skip processing a small portion of events entirely. Remediation Steps: Once the source of the issue was identified, Okta's engineering team immediately began rolling back to the original event delivery service at approximately 7:30 AM PT. The rollbacks were completed at approximately 1:21 PM PT. Any events triggered after 1:21 PM encountered no lag. The remaining events in the new system queue were organically processed by 4:45 PM PT. These actions successfully addressed the issue, and normal operations were restored by 4:45 PM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta has currently implemented the following: Added and improved alerting related to Okta webhook delivery Additionally, we are reviewing and enhancing additional internal alerting processes and procedures to prevent this issue from recurring in the future. To further enhance reliability, we are implementing stronger validation and assurance practices for new system component change controls.