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 process failing

SA-14032

Summary



An agent process that was previously working now fails with errors due to an failed instance of a certain rule.


Error Messages



Failed to find instance Class.RuleName of type Rule-Obj-When.


Steps to Reproduce

  1. Upload an element into the agent queue.
  2. Open SMA and select to delay the agent of interest.
  3. Select the Requestor link and click the radio button aligned to the Requestor matching the agent.
  4. Click Tracer button. Observe the instance error.

Root Cause



An issue in the custom application code or rules. The issue is that the agent schedule and agent record were not synchronous and the agent running did not have the proper access to see the rules of interest.

Resolution



Perform the following local-change:
  1. Update the agent rule to specify the necessary access group on the security tab.
  2. Delete all linked agent schedules that are linked on the nodes tab.
  3. Restart the JVM and test the scenario of interest.

 

Published September 11, 2015 - Updated October 8, 2020

Was this useful?

0% 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