4 May 2026
Initial rollout date: 23rd May 2026
Estimated completion date: 25th May 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: 15.0.0.2418
Provisioning worker: 15.0.0.1149
Changes 
Improved context handling and CBK alignment
As part of ongoing data model alignment, we have improved how contexts are identified to ensure consistency between legacy and current formats. Contexts generated using different identifier formats are now merged, with the latest value from Enterprise Server used as the authoritative source.
Additionally, ContextAssignment and ContextOwner data are now included in the migration, ensuring consistent context relationships across the platform.
These changes eliminate duplicate contexts, improve data consistency, and ensure accurate reporting and relationship mapping across analytics.
Resolved bugs and issues 
Preview, provisioning, and import non-functional
There was an issue where despite the Cloud Application Gateway being operational, the preview, provisioning, and import processes were non-functional. The appsettings.customer.json configuration file had a mismatch. The dedicated instance name was set to a different value than Default causing the issue.
Correcting the configuration resolved the problem, and the preview, provisioning, and import capabilities have been restored.
INC-313169
Connectivity issues due to proxySettings ignored
The proxySettings configured in the appsettings.customer.json file were being ignored, resulting in connectivity failure.
The issue was resolved by reconfiguring the Cloud Application Gateway services to make them operate under a Service account. This allowed proper proxy usage and restored connectivity.
INC-312866
HR import not working
There was an issue with the HR import not working correctly. The issue was caused by faulty expression handling the Corporate_mobile_number field. Some identities had values shorter than expected resulting in the StartIndex cannot be less than zero error.
The issue was resolved by correcting the data causing errors or by adding validation logic allowing to handle shorter values correctly.
INC-313028
Calculation warning for terminated identities
There was an issue with calculating terminated identities. The system continuously attempted to create account assignments for terminated identities.
The assignment handling for terminated identities has been corrected, preventing unnecessary calculations and errors.
INC-311754
Initial import error after the migration to Horizons
There was an issue with the initial import after the migration to Horizons. The problem was caused by an initialization flaw in the migration process, resulting in a GraphQL-related database object being created before the required table existed.
The issue was self-corrected with export mapping initiation that created the necessary table.
INC-312875
Effective time handling after enabling Horizons
We identified an issue where the EffectiveTime could be incorrectly set when enabling Horizons. This occurred because the system updated the effective date before a valid creation timestamp was available for the identity.
We have updated the process to wait until the identity is delivered with a valid creation timestamp before setting the EffectiveTime, ensuring inconsistencies are resolved automatically.
INC-309375