Multiple roles stuck in applied state after applying bulk change on multiple roles in RSA Governance & Lifecycle
Last Modified: 2024-12-09
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 391Number of Views Looping fulfillment workflows cause multiple issues in SecurID Governance & Lifecycle 336Number of Views RSA Authenticator 6.2.4 for Windows Administrator Guide 48Number of Views Troubleshooting Wildfly clustering Multi-cast connectivity for RSA Via Lifecycle and Governance 195Number of Views How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… 158Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?