Multiple roles stuck in applied state after applying bulk change on multiple roles in RSA Governance & Lifecycle
Article Number
Issue
After applying bulk changes on multiple roles involved in one request at the same time.
The request completes, but the roles are stuck in applied state.
Cause
If the system is restarted during the creation of change requests related to the Role changes it may leave the Role in applied state.
Bulk Role changes create workflow watches that keep monitoring the CR completion delete the role_id from t_av_roleversion when the change request is completed. If the system gets restarted the watches may not be cleared.
Resolution
Note:- user must take a backup from below query
select cr.id,cr.name,rv.* from t_av_roleversions rv join t_av_change_requests cr on rv.cr_id=cr.id where rv.state='A' and cr.current_state='CO' order by cr.id;
Related Articles
Roles stuck in Applied state in SecurID Governance & Lifecycle 376Number of Views Looping fulfillment workflows cause multiple issues in SecurID Governance & Lifecycle 325Number of Views install the enterprise co-ordinator hangs at end when communication with the data base has access to firewall ...sees the … 12Number of Views Access Fulfillment Express (AFX) does start after applying Patch 11 or higher to RSA Via Lifecycle and Governance 6.9.1 3Number of Views Creating Custom Aveksa Entitlements in RSA Governance & Lifecycle 6Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?