Question

4
Replies
100
Views
Close popover
Avisek Mondal (avisekmondal)
Cognizant Technology Solutions
System Architect
Cognizant Technology Solutions
IN
avisekmondal Member since 2008 21 posts
Cognizant Technology Solutions
Posted: January 22, 2020
Last activity: January 27, 2020
Closed
Solved

SLA Agent behavior

In our application we have 4 nodes. User reported an issue that they are not getting mails and we found out that the SLA events were not processed. When we checked SMA, we saw that there was no Last Run Finished time getting printed for Pega-ProCom.ServiceLevelEvents agent. So, we followed the below article, deleted the data agent instances for Pega-ProCom agent from all the 4 nodes and restarted the server. Now we could see that the last run finished time getting printed.

https://community.pega.com/support/support-articles/agent-does-not-process-sla-items

But when we query the pr_sys_queue_sla table with item status as 'Scheduled', we see the count getting decreased and again getting increased and this continues. I mean : at one time lets say its 428567, after some time it is 428562, again it is 428569, again 428564 like that, and its not uniform. The pending items are from 1/4 to 1/15 and there is around 400K+ records in that table.

Is there a way we can determine if the agent is running and processing the items correctly? The max attempt is given as 1.

We are using 7.1.8.

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.