The requirement in this case is the Service REST that is handling calls from consumers needs to have a 6-second timeout. If the Service Activity can not complete in 6 seconds, it needs to terminate. The SLAs for the consumers is under 2 seconds. So, the consumer who initiated the request has already terminated it and is "no longer listening". But, the request is still churning in Pega. We want to get these requestors back into the pool ASAP.
How can this be implemented in Pega? Needs to be synchronous.
The service activity has internal connect calls to other applications, so there might be something that can be done on those steps in the activity. But, is there any configuration that can handle terminating an active.
***Updated by moderator: Lochan to add Category; added enhancement details***
An enhancement has been filed for this. I have added the request number in the Related Support Case Number field under the original post. Please work with your Account Executive, by referencing that number, to know the enhancement status!
Lochan | Community Moderator | Pegasystems Inc.