Closed
Agent Not Running in Scheduled Interval Post Cluster Restart
Hi Team
One of the Advanced agent which is configured to execute on fortnightly at 03.00 AM AEST that We noticed the agent scheduled window getting reset every time once node restart happening in production environment which results unwanted cases getting processed.
For instance, If the cluster restart happened in 04-Nov-2017 (Saturday), and the agent is scheduled to run on 13-Nov-2017 (Monday), then in this case after the cluster restart we observed that agent got re-scheduled on 06-Nov-2017 which it supposed to run on 13-Nov-2017.
One of the Advanced agent which is configured to execute on fortnightly at 03.00 AM AEST that We noticed the agent scheduled window getting reset every time once node restart happening in production environment which results unwanted cases getting processed.
For instance, If the cluster restart happened in 04-Nov-2017 (Saturday), and the agent is scheduled to run on 13-Nov-2017 (Monday), then in this case after the cluster restart we observed that agent got re-scheduled on 06-Nov-2017 which it supposed to run on 13-Nov-2017.
Regards
Vamsi G
***Updated by moderator: Lochan to update Categories***
Posted: 7 years ago
JPMorgan Chase & Company
JPMorgan Chase & Company
US
Hi Vamsi,
Is there any difference is Agent configuration and agent schedule rule configuration, also please check is node id is changing after restart which result to taking Agent configuration instead of agent schedule rule.
Posted: 7 years ago
ANZ
ANZ
IN
Hi Sudhakar
I can confirm you that, node ID remains same post restart of server.Also, it looks configuration also same in agent rule and schedule instance.
Regards
Vamsi G
Posted: 7 years ago
PEGA
Pegasystems Inc.
US
It is an interval (every n days/weeks/whatever at 3pm) not a date time. This sounds like an improvement request. The time restarts at startup. So it starts on the first Monday after the restart
Can you provide the configuration details?
screenshot if possible?