Delayed Routing to a WB
Hi,
I was looking for a solution to one of my issues which is not tracable. Im not very sure on where the problem is. Request your guidance on the same.
Below are the course of actions that we perform in our flow:
1) We get data from an external system through a SOAP service.
2) In our servie activity, we store the data into our Pega work table.
3) After the save, we launch a flow as the last step of the activity. (Till here - all good. Data is getting saved to the work table and the flow is getting launched.)
4) In the flow, the first shape is a router. It routes the case to a work basket.
5) After the router we have few more shapes where the user logs in and picks up the case from the routed WB and processes the case.
The issue is with the step 4 !!! I can see the work table getting updated with the new incoming data. I can also see in the tracer that the flow is getting launched and the WB routing has taken place and flow goes on 'Idle' mode.
But in my portal, when I check that WB, I CANT see this newly routed case. When I check the Assign-Workbasket table, I cant find this case.
After a delay of may be 20mins- 2 hrs (variable each time. Sometimes even half a day !!!), I can see that case in the expected WB.
Can you please help me to find the cause of this delay ?
Thanks&Regards,
Rashmi
Hi,
I was looking for a solution to one of my issues which is not tracable. Im not very sure on where the problem is. Request your guidance on the same.
Below are the course of actions that we perform in our flow:
1) We get data from an external system through a SOAP service.
2) In our servie activity, we store the data into our Pega work table.
3) After the save, we launch a flow as the last step of the activity. (Till here - all good. Data is getting saved to the work table and the flow is getting launched.)
4) In the flow, the first shape is a router. It routes the case to a work basket.
5) After the router we have few more shapes where the user logs in and picks up the case from the routed WB and processes the case.
The issue is with the step 4 !!! I can see the work table getting updated with the new incoming data. I can also see in the tracer that the flow is getting launched and the WB routing has taken place and flow goes on 'Idle' mode.
But in my portal, when I check that WB, I CANT see this newly routed case. When I check the Assign-Workbasket table, I cant find this case.
After a delay of may be 20mins- 2 hrs (variable each time. Sometimes even half a day !!!), I can see that case in the expected WB.
Can you please help me to find the cause of this delay ?
Thanks&Regards,
Rashmi
***Updated by Moderator: Lochan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***