Skip to main content

14th September 2026

· 2 min read

badge

Next scheduled release

Initial rollout date: 12th October 2026
Estimated completion date: 16th October 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.176
Provisioning worker: 16.0.0.107

Resolved bugs and issues ​

Import failing due to threshold violation​

We have fixed an issue where import thresholds configured with a 24-hour interval were misinterpreted as 24 days. The interval value was parsed using .NET's TimeSpan.Parse(), which does not support hours of 24 or greater, so the hours were reinterpreted as days instead. The 24:00:00 was stored as 2,073,600 seconds (24 days) rather than the expected 86,400 seconds, or 24 hours. This caused import threshold violations to trigger incorrectly for intervals of 24 hours or more. The fix replaces the TimeSpan.Parse() with manual HH:MM:SS parsing that correctly derives the interval in seconds.

INC-318721

Provisioning failure when manager attribute is mapped to null​

We have resolved an issue related to a recent Cloud Application Gateway (CAG) update where provisioning tasks failed to update their status when the manager attribute was mapped to null, preventing affected accounts from being created.

INC-319236

Import failing during the event generation stage​

We have fixed an issue where imports could intermittently fail during the event generation stage. The failure was caused by an invalid execution plan in the underlying stored procedure. The procedure has been corrected to prevent the issue from recurring.

INC-317353

Actual direct resource assignments lost after RoPE identity recalculation​

We have fixed an issue where repeated event generation failures could cause identities to lose their Actual Direct resource assignments, triggering unwanted account creation jobs in RoPE. The affected data has been repaired, and the underlying issue has been resolved to prevent the problem from recurring.

INC-318635

Stalling RoPE calculation due to prolonged actual state retrieval​

We have resolved an issue where identity calculation in RoPE could stall or time out while retrieving actual resource assignment data, causing identities to remain in the Pending state. The issue was caused by an expanding volume of expired historical data in an internal assignment table. A cleanup mechanism has been added to prevent this data from accumulating.

INC-316658