Close popover
Guangri Liang (liang)
Sr. System Architect
Pegasystems Inc.
liang Member since 2019 10 posts
Posted: June 25, 2020
Last activity: June 25, 2020

About Rest Service SLA with fallback activity

Hi, Please can somebody clarify the specs about [Rest Service SLA with fallback activity]?

There are three setting items as below and I just write what I found in my confirm test.

1. Maximum duration for service activity(milliseconds) : 

   If a service activity process time exceeds this value, timeout happens with log [Service activity SLA violation, execution took longer than expected. Execution time]. 

   (This service activity itself will not be stopped even after the timeout occurred and it won't return any timeout error to client side.) <<--- Can somebody confirm if what I observed is correct?

2. Maximum consecutive violations.

   On each server node, if the total count for [1]'s timeout exceeds this value, then pega server will execute

   fallback activity. For example, if the value is 3, next time the 4th request come in, then pega server will execute fallback activity.

3. Retry interval(seconds)

    The description about this setting item :[Enter the amount of time, in seconds, to wait before attempted to process the service activity]

    It seems like once the total timeout count exceeds the [Maximum consecutive violations] , Pega server needs to wait for [Retry interval] period for reset the timeout count. I am not sure if my understanding is correct, actually even time passed over the retry interval seconds it seems not get reseted...I hope someone can clarify this part...


Service SLA



***Edited by Moderator Marissa to update Platform Capability tags****

Pega Platform 8.4 Case Management