# Okta: Workflows Telemetry issue

> Okta status incident “Workflows Telemetry issue” on 2025-01-15: impact minor (vendor’s label), -1146 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/okta/incidents/I-9059
Last updated: 2025-01-24T07:04:02Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-01-15 19:06 UTC · Resolved: 2025-01-15 00:00 UTC · Duration: -1146 min
- Updates: 1 · Affected components: Cell okta.com:1, Cell okta.com:2, Cell okta.com:3, Cell okta.com:4, Cell okta.com:6, Cell okta.com:7, Cell okta.com:11, Workflows / Core Service
- [Vendor status page: https://status.okta.com/\#incident/a9C4z000000TXIxEAO](https://status.okta.com/#incident/a9C4z000000TXIxEAO)
- [Company: Okta](https://rewindex.com/company/okta.md)

## Timeline of updates

- **resolved** 2025-01-24 07:04 UTC: 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.

## 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).

- Canonical URL: https://rewindex.com/company/okta/incidents/I-9059
- Citation: Okta, “Workflows Telemetry issue” (2025-01-15 19:06 UTC). Archived by Rewindex: https://rewindex.com/company/okta/incidents/I-9059 (CC BY 4.0).
- Markdown link: `[Okta: Workflows Telemetry issue (2025-01-15)](https://rewindex.com/company/okta/incidents/I-9059)`


---
Canonical: https://rewindex.com/company/okta/incidents/I-9059 · Markdown: https://rewindex.com/company/okta/incidents/I-9059.md · JSON: https://rewindex.com/api/v1/companies/okta/incidents/I-9059 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T18:50:31.909Z