Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identity Governance & Lifecycle
Originally Published: 2020-09-22
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1
Issue
For example,
1. Make a copy of the default "On Hold Review" workflow but with the Review Status changed to Complete.
2. Edit the default user review to set the due date as 1 day.
3. To a default user review associate the escalations to change the review state to hold after 1 day and then change the state to complete after 2 days.
4. Run the review
5. You will see the OnHold escalation triggers but the next escalation does not get triggered.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P11
- RSA Identity Governance & Lifecycle 7.2.0 P05
- RSA Identity Governance & Lifecycle 7.2.1 P01
Related Articles
Review escalation workflows sometimes do not trigger in RSA Identity Governance & Lifecycle 93Number of Views Escalation Workflows randomly fail to trigger in RSA Identity Governance & Lifecycle 46Number of Views Implementation of Reminder Email as Escalations in RSA Via Lifecycle and Governance 67Number of Views Unable to search or sort for reviewer when using Review Results -> Escalations tab in RSA Identity Governance & Lifecycle 11Number of Views When the Escalations column is included in the Change Requests table display, Change Requests with Escalations display as … 40Number 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) RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?