From the error log snippet, I see below error reported:
2017-06-21 21:26:19,371 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ IntTrackFW:01.01.01] ( FlowProblems.Work_.Action) ERROR - Problem flow abort due to system flow FlowProblems being the issue
com.pega.pegarules.pub.PRAppRuntimeException: The flow WaitForEvaluation had a problem on step pyContinueAfterWait of: ** The flow pyCascadingGetApproval had a problem on step ASSIGNMENT63 of: No routing information was provided for this assignment.
I find below related posts in our PSC which refers to configuration for the assignment:
It looks like the issue is coming from the pzGetApproverName activity. When the approval type is Work Group Manager, it will go through step 3 to set the pyApproverName. The java code gets the work group from the OperatorID page. In the case of the Wait shape, it would be the service level agent processing the Wait shape. Do you see the same error when processing the Wait assignment manually as an end user?
I tested the scenario on my system. It works for me when processing the Wait assignment as an end user with the PegaRULES:User4. It fails when processed by the SLA agent though because the OperatorID page would be different. You could add a custom activity after the Wait shape to get the appropriate operator to route to and then use that operator when calling pzApprovalFlowWrapper.
Thanks Carissa & Lalit! I have gone ahead and submitted this enhancement on your behalf and updated the original post with the Feedback ID. You can now take this to your Account Executive for next steps.
This is a known issue when previous assignment (Could be wait shape or normal assignment) is moved by an agent and next assignment is configured as Route to current operator. As the current operator in Agent's case will be System and there is no operator with that name. Hence the issue.
Which Pega version are you using ? You can solve this issue by changing the routing of next assignment.