Resolved -
All tenants have been fully restored and their data pipelines fully re-enabled.
May 6, 03:52 UTC
Update -
All entitlements, tasks, policies, access profiles and other affected objects have been fully restored.
Sync pipelines are fully enabled for all tenants except one, whose Okta sync remains ongoing.
May 5, 16:12 UTC
Monitoring -
Most data pipelines are now fully re-enabled. We are continuing to monitor several tenants which have not completed a full Okta sync since being re-enabled, and are separately in the process of restoring tasks related to affected entitlements.
May 5, 10:57 UTC
Update -
Most data pipelines are now fully re-enabled. We are continuing to monitor several tenants which have not completed a full Okta sync since being re-enabled, and are separately in the process of restoring tasks related to affected entitlements.
May 5, 10:56 UTC
Update -
We have executed a migration to restore entitlements to their original IDs, as well as any objects which referenced those entitlements.
All Okta v2 connectors have been re-enabled, and as they complete their syncs we are re-enabling the full data processing ("uplift") pipelines for affected tenants. We are additionally working to restore any tasks related to the affected entitlements.
May 5, 10:12 UTC
Update -
We are currently testing a migration to restore affected customers.
At this time sync remains disabled on all Okta v2 connectors to prevent further impact.
May 5, 08:20 UTC
Identified -
We’ve identified an issue that, for some customers, caused Okta-group entitlements to be recreated with new IDs. We’re actively restoring the affected policies, Access Profiles and related references. Affected customers should avoid any manual attempts to reinstate these configurations.
May 5, 03:47 UTC