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 384Number of Views Looping fulfillment workflows cause multiple issues in SecurID Governance & Lifecycle 336Number of Views Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle 126Number of Views RSA Authenticator 6.2.4 for Windows Administrator Guide 47Number of Views Business descriptions are applied incorrectly when using a wildcard with an underscore in RSA Identity Governance and Life… 19Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?