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

Email workload distribution is not working as intended



Agent SendEmailsInBulk processes pending emails from table pegadata.pr_data_corr_email.

It creates the number of child requestors specified in the topology to do the actual sending in parallel.

This works well except at the tail end of a run. If the number of emails pending is less than the "total size" (batch size times thread count from topology), all of the remaining emails are processed in only one child requestor.

It has been observed these tail end emails taking 45 minutes to send. The algorithm should continue to process these tail end emails in multiple requestors.

Error Messages

Not applicable

Steps to Reproduce

  1. Set the batch size to 250 and the number of threads to 40.
  2. Run an email campaign with 39,999 emails.
  3. Run the SendEmailsInBulk agent. The first 30,000 will run fast in 40 child requestors. The remaining 9,999 will run in only one child requestor and will take a long time, much longer than the first 30,000.

Root Cause

This is currently working as per the design where the total size = batch size times thread count from topology.


An enhancement request, FDBK-17597, has been created for consideration by Pega Product Management.

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