Review escalation workflows sometimes do not trigger in RSA Identity Governance & Lifecycle
Originally Published: 2019-05-06
Article Number
Applies To
RSA Version/Condition: 7.1.0, 7.1.1
Issue
If the same review is generated and has its review state manually set to Active, the other review escalations trigger as expected and the change in review state is reflected in the review history.
For example,
- Create a rule definition that is initially set to On Hold, changed to Active by the Active Review workflow, and has multiple review escalations.
- Run the review.
- Note the review is changed to Active.
- Note the Review History is not updated.
- The expected review history is as follows:
- Note the review escalation workflows are not triggered:
- The expected behavior is for the escalation workflows to trigger:
Cause
Resolution
Workaround
Related Articles
Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identi… 61Number of Views Running sdcompress; error: 'TRIGGER ERROR' 7Number of Views Escalation Workflows randomly fail to trigger in RSA Identity Governance & Lifecycle 46Number of Views Objects previously collected by Account Collectors and Entitlement Collectors in 6.x are rejected in 7.x of RSA Identity G… 160Number of Views Sub-groups resolution is rejected and Member Type is set to "Account" instead of "Group" for Account Collectors in RSA Ide… 43Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?