on May 9, 2017Article Content
| Article Number | 000034793 |
| Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.x |
| Issue | Change Requests in RSA Identity Governance & Lifecycle have several states. Two of these states are Canceling and Cancelled. The Canceling request state is intended to be a temporary state and the request should transition automatically to the Cancelled state without user interaction. However, there are times when a Request Workflow remains stuck in the Canceling state and does not progress to the Cancelled state. The server may be experiencing performance problems and indicate high CPU usage and a large amount of JVM Heap Memory in use. |
| Cause | There are a variety of reasons a request may become stuck in the Canceling state. If the issue occurs frequently, the cause of the failures should be investigated. Please contact RSA Identity Governance & Lifecycle Customer Support for assistance with investigating these failures. |
| Resolution | A Request Workflow in the Canceling state can be manually moved to the Cancelled state using the following procedure:
NOTE: If you have multiple requests in a Canceling state that need to moved to a Cancelled state, please contact RSA Identity Governance & Lifecycle Customer Support for assistance. |