OpenGov incident
Enterprise Asset Management: User layers overwritten when switching to New UI during user impersonation
OpenGov is currently experiencing a minor incident affecting Asset Management (formerly Cartegraph), which began 12d ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified Oct 02, 2026, 01:47 AM UTC
We have identified a behavior in Enterprise Asset Management affecting administrators who use User Administration > Sign in a User to impersonate another user. If an administrator switches to New UI while impersonating a user, that user's saved layers are replaced with the administrator's own layers. This change persists after the impersonation session ends and cannot currently be reversed through the application. Impersonation sessions that remain entirely in Classic are not affected. To prevent this issue, administrators should not switch to New UI while impersonating another user. Remain in Classic for the entire impersonation session, and use "Sign In as Me" to return to your own account before switching to New UI. Users whose layers have already been affected will need to recreate them. Our team is actively working on a fix, and we will provide an update as soon as more information is available. If you believe your users have been affected, please contact OpenGov Support.
- monitoring Oct 08, 2026, 02:43 PM UTC
A fix was deployed on October 5, 2026 that prevents an administrator's layers from overwriting an impersonated user's layers when switching from Classic to New UI during a User Administration > Sign in a User session. Our team is continuing to work on a remaining scenario. If an administrator already has New UI open in another browser tab while impersonating a user, the issue can still occur. Until this is fully resolved, we recommend that administrators close all other New UI tabs before impersonating a user. Remaining in Classic for the entire impersonation session and using "Sign In as Me" before switching to New UI remains the safest approach. This fix does not restore layers that were affected before October 5. Those layers will need to be recreated.
- monitoring Oct 08, 2026, 03:40 PM UTC
We are continuing to monitor for any further issues.