Mandatory Okta Workflows Database Maintenance Scheduled through August 2026

Okta Workflows is executing an AWS-mandated major Postgres database upgrade across all cells. Running workflows and write operations will experience latency for up to 40 minutes during each migration window.

• Okta Workflows
• Okta Classic Engine
• Okta Identity Engine (OIE)
• Database Maintenance
• Cell-Based Upgrade Schedule

What maintenance is scheduled for Okta Workflows?

To maintain standard vendor support and reinforce the resilience of the data layer, Okta Workflows will undergo a mandatory Postgres database version upgrade across all cells. This upgrade process will be executed sequentially, on a cell-by-cell basis, from July 2026 through the end of August 2026.

Maintenance windows are restricted entirely to the designated "off-hours" of each cell's local timezone to minimize operational impact on the business logic

Which dates and cells are in the upgrade schedule?

The upgrade is scheduled during localized cell off-hours. Review the assigned cell and date to identify the planned maintenance window.

• Jul 9, 2026 - FP2 (Okta cell OP2) - COMPLETED
• Jul 9, 2026 - FP1 (Okta cell(s) OP1, OP3) - COMPLETED
• Jul 13, 2026 - FL8 (Okta cell OK8) - COMPLETED
• Jul 15, 2026 - FL16 (Okta cell OK16) - COMPLETED
• Jul 16, 2026 - FL12 (Okta cell OK12) - COMPLETED
• Jul 18, 2026 - FL2 (Okta cell EU1, OK9) - COMPLETED
• Jul 20, 2026 - FL14 (Okta cell OK14) - COMPLETED
• Jul 21, 2026 - FL10 (Okta cell(s) OK5, OK10) - COMPLETED
• Jul 22, 2026 - FG1 (Okta cell OG1) - COMPLETED
• Jul 23, 2026 - FM1 (Okta cell OM1) - COMPLETED
• Aug 22,2026 2:15 PM PDT- FL1 (Okta cell(s) OK1, OK2, OK3, OK4, OK6, OK7, OK11)

NOTE: This schedule is subject to change as the rollout progresses. Please check this page periodically for the most up-to-date information. 

What impact occurs during the database migration?

Active running workflows and write operations will experience elevated latency for up to 40 minutes during the database migration, after which latency will return to normal over the next hour.

Attempts to access the Workflows Console during the upgrade timeframe may result in a 50x errors.

All execution loops will resume processing sequentially and automatically once the database layer comes back online.

Which actions reduce operational impact?

Review the specific cell alignment (above) to identify the exact off-hours date window assigned for the infrastructure's database upgrade.

Ensure the teams are aware that delayed business flows will automatically resume trailing actions post-upgrade, eliminating the need for manual restarts