Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Agent schedule not refreshed after agent rule update



Updates to Agent rule are not getting propagated to corresponding Agent schedule when it is deployed to another environment.

Error Messages

Not Applicable

Steps to Reproduce

  1. Update the access group of an existing agent with a new access group.
  2. Create a product file and deploy the changes to another environment.
  3. Check the agent schedule instance.

Root Cause

In Pega 7.1.6, updates to agents will not be propagated to agent schedules.

Even though this behavior exists in later releases, it is again reverted on Pega 7.2.2 due to consistency issues.


In Pega releases later to Pega 7.1.6 but below Pega 7.2.2, updates to agent will be propagated to agent schedules.

Rest of the PRPC release requires manual deletion of agent schedules to get the changes those are made to agents.

​In this case, the agent schedules will get recreated with latest changes automatically.

Published February 20, 2017 - Updated October 8, 2020

Was this useful?

50% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us