Review escalation workflows sometimes do not trigger in RSA Identity Governance & Lifecycle
Originally Published: 2019-05-06
Last Modified: 2023-11-30
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
Escalation Workflows randomly fail to trigger in RSA Identity Governance & Lifecycle 50Number of Views 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 Monitoring page performance issues in RSA Identity Governance and Lifecycle 69Number of Views How to interpret the RSA Identity Governance & Lifecycle User Access Review User Entitlement Coverage report. 41Number of Views Raw Data counts and Task Result counts in Role Collector data runs are sometimes inconsistent in RSA Identity Governance &… 49Number 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 Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities
Don't see what you're looking for?