retry mechanisms work in connect REST?
How the retry mechanisms work in connect REST?
Like we have to retry if the consuming service is down and we have to track how many times it has been retried?
- Modify ConnectionProblem OOTB flow rule to handle the connectivity failures
- Execute all the connect REST rules through the assignment. This approach will help us to achieve a retry mechanism using Service level agreements. After the successful retries, if the issue still persists, route the case to exception workbasket.
- Create a new data table to record the exceptions encountered. Create an agent activity to monitor the data table and send an email in a timely fashion to the administrator about new entries.
reference- https://collaborate.pega.com/question/connect-rest-error-handling-across-application-design-query
I am looking for points 2 and 3, but I have no idea how to design can someone provide inputs or doc screenshot if they have implemented in their application.
It would be very helpful.
***Edited by Moderator: Pallavi to update platform capability tags***