Stage Level SLA - Agent process Goal and Deadline at the same time regardless of the defined time intervals

We have defined stage level SLAs. Fo rtesting in SLA we defined Goal - 8 minutes, Deadline - 15 mins. In development server this SLA is processed by agent as expected. Example if stage is reached at 8:00AM then Goal will be reached at 8:08AM and Deadline 8:15AM.

But once we move code to QA and Pre-Prod environments these SLAs acts differently. For example if stage reached at 10:00AM Goal should be reached by 10:08AM and Deadline by 10:15AM. But in both the environments Agent wont pick the case untill 15-20 minutes passed after reaching the stage. Then it process the case and applies Goal and Deadline at the same time. 

Some cases are processed properly but most encounter mentioned issue. Appreciate if someone can help to figureout this issue. Thank you.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

December 14, 2016 - 12:30am

Hi Mkarunagama,

Have you raised an SR regarding this. If not, please create under My Support portal.



December 14, 2016 - 2:15am

Adding to Prudhvi's comments- 

If you raise an SR related to this query, please feel free to share the SR number here as a comment so that we can track the SR within the thread for you.

~Vidyaranjan A V  | Community Moderator  |  Pegasystems Inc.

Vidyaranjan | Community Moderator | Pegasystems Inc.

December 14, 2016 - 8:44am

Have you looked at the queue item created in QA to confirm it has the correct time? Was the work object locked when the agent initially tried to process it? Is there a backlog of queue items that the agent is not able to process all of them on time?