suppose your Connect Rest is failing due to some resource unavailability how will you configure the scenario like it should retry for 3 times and then move to a diff workqueue
suppose your Connect Rest is failing due to some resource unavailability how will you configure the scenario like it should retry for 3 times and then move to a diff workqueue,but the response properties should be present it should not be like the case should start from the begining
Pegasystems Inc.
CA
Please check the attachment.
Run Data transform - Invoke the REST connector.
Max Attempts assignment - You can connect to Run data Transform or end shape based on your requirement.
I hope this helps!
Cognizant
IN
@RameshSangili so here I didnt get one thing is this the Response data transform which we are calling in run DT shape?and how this flow works like first its running DT then going to decision shape then also wait shape is also having a incoming connector towards the Run DT shape and about Max Attempts assignment how things will happen there?
Pegasystems Inc.
CA
if the connector is unsuccessful, it goes to wait shape and waits for 10 minutes or so based on your requirements, then retries; that's why it goes back to Run Data transform to invoke the connector again. Once the max Attempts are reached, then it goes to the Work queue
Updated: 9 May 2024 14:10 EDT
Infosys Limited
IN
You can also customize the ootb connection problem flow which is there in the connector rule for your requirement. Basically this flow gets executed when an connector gets invoked through the flow rule and an exception occurs.
You can find this rule in the connector rule form. As per existing OOTB, if the service gets failed due to non availability it would get retried based on the sla attempts and if attempts reached it moved to problem flow work basket. Please go through this flow and you would get to know it.
Cognizant
IN
@P.Siva.Praveen in case of the OOTB flow how can we make it retry for 3 times specifically?And what if my connector is not invoked from a flow I am calling a utility to invoke it then?
Infosys Limited
IN
For OOTB flow, as i said before SLA would take care of the attempts. If you want to configure the attempts as you need you need to customize the SLA.Please go through the below article: https://academy.pega.com/topic/resolving-flow-issues-using-problem-flows/v2?
If connector gets invoked from activity then on the jump condition increment the attempt counter either in param or clipboard property and then execute the wait method in the activity to wait for some time.
Then, invoke the connector again till the attempts are reached. After reaching the attempts invoke the problem flow (your customized version if required) using the flow new method.
Cognizant
IN
@P.Siva.Praveen can we execute wait method in activity?
Infosys Limited
IN
Yeah, we can..there is wait method.