14th October 2026
Initial rollout date: 12th November 2026
Estimated completion date: 16th November 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.273
Provisioning worker: 16.0.0.129
Changes 
Instance ID displayed next to workers in System Heartbeats
The System Heartbeats widget in the Operations dashboard now displays the instance ID next to each worker service. Previously, the Import Worker Service and Provisioning Worker Service could appear twice in the widget when two Cloud Application Gateway (CAG) instances were sending heartbeats, one hosted by the customer and one hosted by Omada.
This allows you to distinguish between the instances and avoids confusion about duplicate worker services.
Resolved bugs and issues 
Identities losing organizational unit and policy-driven assignments
We have fixed an issue where identities could lose their organizational unit and the related policy-driven assignments after an import that received both contexts and context assignments. In this case, a context was received with a new query ID while the existing context assignment still referenced the previous query ID. The lookup could not find a valid owner for the context and removed the previous lookup data. When the new context assignment was received later in the same import, the required lookup data was already missing, so the context assignment was not stored.
The processing of contexts and context assignments received in the same import has been corrected to prevent the issue from reoccurring.
INC-319352
Organizational unit changes not applied to employments
We have fixed an issue where a change of the organizational unit in the source system was not applied to the employment in Omada. When the parent business key of a context changed, Enhanced Delta updated only the reference to the latest version of the original parent and did not look up the new parent. As a result, the parent context ID in the lookup data still pointed to the original parent, and employments kept the previous organizational unit, which could affect access based on the organizational unit.
The Enhanced Delta now updates the parent reference when the parent business key changes.
INC-320008
Cleanup import profile reported as failed
We have fixed an issue where the cleanup import profile was reported as failed even though all cleanup operations were completed successfully. An incorrect status update prevented the process from reporting completion, so the task timed-out and was marked as failed. No operational data was affected.
The issue has been resolved and the cleanup status is now reported correctly.
INC-319948
Cloud Application Gateway automatic update failing in proxy environments
We have fixed an issue where the automatic update of the Cloud Application Gateway (CAG) could fail in environments where outbound connections are routed through a proxy. The worker manager application, which handles the upgrade process, was unable to connect to the Omada Cloud Service, while the import and provisioning workers connected successfully.
The issue has been resolved with the updated CAG version.
INC-319706
RoPE calculation stalling due to outdated statistics on indirect resource assignments
We have fixed an issue where identity calculation in RoPE could stall when a large number of new versions were created in the indirect resource assignment table, for example, in environments that run imports frequently. The database statistics for this table were not refreshed fast enough, which could cause an inefficient query execution plan and lead to timeouts.
To resolve the issue, the statistics are now updated as part of the indirect resource assignment calculation on each import.
INC-316658
Provisioning dashboard showing incorrect operation for a task mapping
We have fixed an issue where the Provisioning dashboard showed the original operation of a provisioning task instead of the operation set by a task mapping. In review mode, the operation was displayed incorrectly until the task was reviewed. The operation that was actually executed was correct, and only the display was affected.
The dashboard now shows the operation set by the task mapping.
INC-319532
Incorrect job counts in Processed last hour and Processed last 24 hours
We have fixed an issue where jobs were counted twice in the Processed last hour and Processed last 24 hours values when relayed connectivity was enabled. The list of jobs in the grid showed the correct number. The counters now show the same number of jobs as the grid.
INC-318786
Identity processing failing after a person is moved between OIS identities
We have fixed an issue where the Identity Processing step of an import could fail repeatedly when a person was moved from one OIS identity to another and the previous identity was renamed in the same import, for example during an employee or contractor conversion. The previous identity remained linked to the person and took over the OISID of the new identity instead of keeping its own. When this identity was processed, the safeguard that prevents an OISID from changing, which would otherwise create a duplicate identity in OIS, stopped the batch. As a result, identities in the affected batch were left unprocessed, which delayed provisioning and credential delivery.
An identity now retains its own OISID unless it is matched through a joining attribute.
INC-320147
AD import not delivering attributes to ODW due to message size limit
We have fixed an issue where an AD import could complete without making new attributes, such as extension attributes, available in ODW. During lookup processing, the result message exceeded the maximum message size allowed by Azure Service Bus (1 MB), so it was rejected with the MessageSizeExceeded error and the affected data was not delivered.
The issue has been resolved, and large lookup results are now handled correctly.
INC-319850
Account type not recalculated when an extension property used in account join rules changes
We have fixed an issue where an account was not reclassified to a different account type after the value of an extension property used in the scope of account join rules changed, for example, when an account was moved to a different organizational unit. The value of this property was not included in the calculation of the configuration hash code. As a result, Enhanced Delta did not detect a change affecting the account join and processed the account through the faster workflow without recalculating the join, so the account kept its previous account type.
The issue has been resolved by including the value in the configuration hash code calculation.
INC-316816