rewindex

CompaniesOktaIncidents

Okta: Workflows Telemetry issue

MinorStatus: resolvedStarted Resolved (-1146 min)1 updatestatus.okta.com (opens in new tab)

Affected components: Cell okta.com:1Cell okta.com:2Cell okta.com:3Cell okta.com:4Cell okta.com:6Cell okta.com:7Cell okta.com:11Workflows / Core Service

Timeline of updates

  1. resolved

    The Okta Workflows team became aware of missing telemetry affecting customers on OK1, OK2, OK3, OK4, OK6, OK7, and OK11 between 6pm and 1am PT on January 14th-15th, 2025.

    During this time, your flows continued to process properly. It may appear that flows did not execute during this timeframe. Telemetry processing has since been restored.

    Root cause information:

    We sincerely apologize for any impact this incident has 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 January 14th at 4:10 pm PST, Okta was alerted to an issue where 8% of Workflows execution history messages were unable to be processed in Cells OK1, OK2, OK3, OK4, OK6, OK7, OK8, OK11. This could result in the appearance that workflow executions were stalled or lost. Workflows continued to execute properly.

    Root Cause Summary

    Based on our investigation and findings, the root cause of this issue was due to a configuration error within services managed by a 3rd party provider during a maintenance window.

    Remediation Steps

    Immediately upon receiving alerts of network disruptions, Okta Engineering escalated the issues with our provider and worked to implement internal mitigations. Okta worked directly with our provider to mitigate the issue and confirmed full service restoration. Okta's internal mitigations restored full service to the affected cells by 5:50 pm PST on January 14th.

    Preventative Actions

    Okta will continue working with our third-party service provider to enhance monitoring and expedite the detection of georegional issues with the queuing system. Additionally, we have updated our operational processes to further improve service recovery times. In parallel, we are rolling out a new, more resilient message delivery system for flow execution history data, reducing our dependency on this specific service.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.okta.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Okta, started 2025-01-15 19:06 UTC, resolved after -1146 min, 1 update(s).

Title
Workflows Telemetry issue
Vendor
Okta
Date
URL
https://rewindex.com/company/okta/incidents/I-9059

Okta profileRecent Okta incidentsAll outages on January 15, 2025Okta in January 2025MarkdownJSON