Skip to main content

6 August 2026

· 2 min read

badge

Next scheduled release

Initial rollout date: 3rd September 2026
Estimated completion date: 7th September 2026

To receive updates about new posts and release notes, subscribe to our RSS feed: https://documentation.omadaidentity.com/horizons-release-notes/rss.xml

Cloud Application Gateway version
Import worker: 16.0.0.102
Provisioning worker: 16.0.0.50

Resolved bugs and issues ​

SAP HCM failing import​

There was an issue with the SAP HCM import failing during the adaptation stage. As a result, all following scheduled imports were aborted. The issue was caused by the EsAdapter service user's group losing access to the Systems entity, so it could not retrieve export mappings for the Omada Identity system.

The issue has been resolved by restoring the EsAdapter service user's group access to the Systems entity.

INC-317432

There was an issue with imports failing due to timeouts. The issue was caused by the AccountJoin duplicate-key conflict. When an identity was deleted in the source system and later re-created with a new business key, the original AccountJoin record, which was retained in a deleted state, conflicted with the unique index on AccountId. The new AccountJoin could not be created

The AccountJoin behavior was corrected to mitigate the import timeout issue.

INC-314030

Actual Direct assignments lost after import adapting-phase failures​

There was an issue where Actual Direct assignments for identities imported from the Active Directory source system became unconfirmed following import adapting-phase failures.

The missing resource assignments were recalculated and manually restored. Additionally, terminated identities were remapped using the useridWH extension attribute to join accounts correctly. The repopulation process has been extended to also be triggered by the AccountJoin changes.

INC-314133