Mandatory Okta Workflows Database Maintenance Scheduled through July 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 15 minutes during the migration.

• Okta Workflows
• Okta Classic Engine
• Okta Identity Engine (OIE)

To maintain standard vendor support and reinforce the resilience of our data layer, Okta Workflows will undergo a mandatory Postgres database version upgrade across all cells. This upgrade process will execute sequentially on a cell-by-cell basis over the month of July 2026. This upgrade must be completed by the end of July.

To minimize operational impact on your business logic, maintenance windows are restricted entirely to the designated "off-hours" of each cell's local timezone. During this localized database migration, the Workflows UI Designer interface will remain online and fully accessible.

Dates & Impacts

The upgrade is scheduled during localized cell off-hours throughout July 2026. 

• Jul 9, 2026 - FP2 (Okta cell OP2) - 10AM PDT
• Jul 9, 2026 - FP1 (Okta cell(s) OP1, OP3) - 8PM PDT
• Jul 13, 2026 - FL8 (Okta cell OK8) - 11AM PDT
• Jul 15, 2026 - FL16 (Okta cell OK16) - 9:30AM PDT
• Jul 15, 2026 - FL14 (Okta cell OK14) - 8PM PDT  
• Jul 16, 2026 - FL12 (Okta cell OK12) - 8PM PDT 
• Jul 18 - FL2 (Okta cell EU1, OK9) - 10AM PDT
• Jul 19, 2026 - FL1 (Okta cell(s) OK1, OK2, OK3, OK4, OK6, OK7, OK11) - 8PM PDT 
• Jul 21, 2026 - FL10 (Okta cell(s) OK5, OK10)  - 8PM PDT 
• TBD - FG1 (Okta cell OG1) 
• TBD - FM1 (Okta cell OM1) 

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

Active, running workflows and write operations will experience latency for up to 15 minutes during the database migration.  

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

Recommended Actions 

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

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