@TanyaS58 okay then browsing cases not required, this exceptional handling flow is each case. Each of your case will hit api and pass through this exceptional handling flow.
Yes if you are wait shape, standard QP is enough.
For updating status you can either configure in any of the assignment shape or use updatestatus shape in the flow. The status update can be handled in your way but ensure that you are following best practice.
@Anoop Krishna but I am still not getting one thing is that what logic do I need to go within the QP activity:1)how to call the connector (do i need to call the same data page that is sourced by the connector) and how will we the flow resume to the normal scenario when the API is successful and that update case status do i need to use after background processing shape?
@TanyaS58 yes right, api exceptional handling and case status update is handled at each case level. There is no dependency on other cases, so not required to browse cases. Whether api is successful or not with our design approach will be decided at each case level.
@Anoop Krishna and also one more thing since i am using wait shape so whatever cases that are failing api and then status is changing to Pending investigation and that case stays in deferred wq for an hour and after that the same case will be reprocessed via qp everytime so thats why looping we are not using?
@Anoop Krishna thanks for answering promptly I will try this approach and post here
@Anoop Krishna have created a separate query section for the continuation of this issue:
Does the standard Queue Processor does not support tickets? | Support Center please go through this link