View Help PDF ( 2.3M B)

During a managed review, there are some asynchronous processes are that are kicked off behind the scene. If the requests from the asynchronous processes fail, users are not notified by default. To troubleshoot such a scenario, follow these steps.

Enable Notifications for Stalled Processes

Whenever there is any failure in a long-lived process, the process operation is stalled and can be viewed in Livecycle Administration Console. You can debug stalled processes. (See Working with stalled operations and branches and Configuring notifications for administrators in LiveCycle ES2.5 Administration Help .)

Debugging Stalled Review, Commenting, and Approval Processes

After setting up notifications for stalled processes, the next step is to debug/recover from the stalled processes. Once you receive an email for a stalled operation, complete these steps:

Identifying if a stalled process is owned by Review, Commenting, and Approval building block:

1. Log in to LiveCycle Administration Console.

2. Navigate to the stalled operations under LiveCycle Process Management ES2.

3. Locate the stalled operation identified with the action id as mentioned in notification email.

4. Note the associated process name.

   The process name contains the name of the application. For example, ReviewCommentingAndApproval/processes/core/AssignTaskToReviewer - 1.0. If the name of the application is ReviewCommentingAndApproval then it is a process owned by the building block.

5. If you are using custom assign task processes, then the name of the application is the name of custom application that contains the custom assign task operations.

Identifying the error:

1. Log in to LiveCycle Administration Console.

2. Navigate to stalled operations under LiveCycle Process Management ES2.

3. Locate the stalled operation identified with action id as mentioned in notification email.

4. Click Stalled Operation Error Details to see the error details.

5. Errors as "Java heap space: java.lang.OutOfMemoryError: Java heap space", or "User Not Found", or any other error, reflect a state of system that has been corrected. Errors such as “the heap size has been increased” or “the user has now been created” reflect a corrective patch has been applied.

6. You can retry the stalled operation

Identifying the Review Associated with failed process

If a stalled process is not recoverable, recovery time is lengthy, or you want to restart the review process, first, identify the review associated with the stalled process. The Review, Commenting, and Approval building block uses many short-lived and long-lived processes but only stores some of the process IDs in its database. (This is due to a technical limitation.)

The building block stores process instance IDs of processes that assign tasks like the AssignTaskToReviewer, AssignTaskToApprover, AssignTaskToInitiator processes. If a stalled process is one of the processes, invoke the Get Review By Process ID operation from the Review Commenting & Approval Core service. The operation takes the process ID as input and returns the Review Context or review ID of the associated review.