Justin Gaupp (JustinG0)

JustinG0 Member since 2014 6 posts
Posted: April 15, 2016
Last activity: August 25, 2016
Posted: 15 Apr 2016 14:33 EDT
Last activity: 25 Aug 2016 7:21 EDT

What would cause the Master Agents to stop running?

What would cause the Master Agents to stop running? In our system, I've noticed in the SMA that the requestors for master agents (including Master for Requestors, RecentsDaemon, ManagementDaemon, and PassivationDaemon) will have "Last Accessed" values that are days past, showing no recent activity from them. One thing I've noticed in correlation with these symptoms is that certain Pega agents (SystemPulse, AgentsBulkProcessing, etc.) will also have a last run time close to the stopped master agents, and the "next run time" value is in the past. I'm guessing this is related, since one of these master agents is responsible for scheduling agent run times as well. We'll also see the "Recents" explorer in the Dev portal not updating, which again is handled by a master agent.

Message was edited by: Marissa Rogers - added Category, moved from Mesh Help

Case Management
Moderation Team has archived post, 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.