Monitoring Agents that are running but locked up and no longer have a next run time
We are consistently running into a situation where an Agent is enabled, no exception has occurred but the Next Runtime is no longer populated and the agent no longer runs. While we are trying to figure out the root cause because this happens to our custom agents as well as OOB agents, we need a way to get notification that the agent is not scheduled to run again. In the image below, we would have the green check and everything would be filled out but there would be no Next run time and no Exception info. We are running PRPC 7.1.7.
We currently use AES but aren't sure if AES can generate alerts for agents in this scenario. Any help is appreciated.
Pegasystems Inc.
IN
American Express
US
We suspect that the activity of the last run is not completing but this happens randomly and without notification so it's difficult to debug. I have seen it happen with our activities as well as OOB like SystemPulse. I was hoping that we had a way to get notified when the previous activity doesn't complete or AES can tell that an agent hasn't run when it was supposed to.
Pegasystems Inc.
US
Hi,
If it is an agent failure do you see any alerts being generated?
| PEGA0010 | Agent Disabled | Agent processing disabled because of execution errors. |
Do you see this alert in the alert logs?
Thanks,
Mukul
American Express
US
Just a follow-up. I still haven't received an answer to this issue/question other than it's probably not possible to us AES to monitor the above error condition.
Pegasystems Inc.
IN
One thing is sure, if your activity encountered any issue, then the agent will stop and next run time will be empty.
However, given the fact, both custom and OOTB agent is showing the same challenge, that gives a question mark whether something more is going on here or not.
Can you enable the following loggers and wait for the issue to occur and then share the log ?
com.pega.pegarules.session.internal.async.BatchRequestorTask