Skip to main content

Managing Concurrent Campaign Data Flow Runs

Suggest edit
Updated on March 25, 2022

To optimize performance and stability of your Pega Customer Decision Hub application, the number of campaign data flows which run concurrently is limited. You can adjust the number of concurrent data flows and the retry interval by editing the related Dynamic System Settings.

Pega Customer Decision Hub
Note: The Dynamic System Settings listed below apply to all outbound, multi-channel, and self-optimized campaigns defined in your application.
  • MKTMaxAllowedBatchDFs - Edit this setting to change how many campaign data flows can run concurrently. By default, ten runs can be active at the same time, and any additional data flows are paused for the duration defined in the setting MKTDFRetryInterval.
  • MKTDFRetryInterval - Edit this setting to change how soon Pega Customer Decision Hub will attempt to execute a data flow which was paused because it exceeded the number of data flows defined in MKTMaxAllowedBatchDFs. By default, the retry interval is 30 minutes. After the inverval passes, Pega Customer Decision Hub checks the data flow availability again, for the number of times defined in the setting MKTDFNumRetries.
  • MKTDFNumRetries - Edit this setting to change how many times Pega Customer Decision Hub will attempt to execute a data flow which was paused because it exceeded the number of data flows defined in MKTMaxAllowedBatchDFs. By default, the number of retries is 5. After the specified number of retries, the campaign run fails and an email notification is sent to the operator who triggered the run.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us