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

Agents getting stuck affecting Segment execution

SA-25429

Summary



DeferredSegment Agent periodically does not finish assignments and causes a failure to execute in other Segments.

Error Messages



Not Applicable.

Steps to Reproduce



Run campaigns and the Agents are getting stuck randomly.

Root Cause



System Pulse and other Agents are getting stuck so the synchronization is failing across all the nodes. Increasing the Agent thread pool size would ensure that the multiple threads, if spawned can run in-parallel.

Resolution



Set prconfig configuration agent or threshold to 50.

Published August 23, 2017 - Updated December 2, 2021

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