Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Limiting active data flow runs

Updated on May 17, 2024

Ensure the optimal use of system resources by limiting the number of concurrent active data flow runs that are allowed for a node type, such as Batch or Search. If the limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can start.

By limiting the number of active runs, you can ensure that you do not run out of system resources, for example, due to large numbers of batch data flow runs.

For more information about the max_active_runs dynamic system settings that define these limits, see Data flow run limits.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the SysAdmin category, and then click Dynamic System Settings.
  3. In the Setting purpose column, click the Filter icon.
  4. In the Search Text field, enter max_active_runs, and then click Apply.
  5. Perform one of the following actions:
    • If the dynamic system setting that you want to change is available in the table, click the row for that setting and go to step 7.
    • If you want to add a dynamic system setting that is not in the table, go to step 6.
  6. Add the dataflow/<node_type>/max_active_runs dynamic system setting for a node type:
    1. On the Dynamic System Settings tab, click Create.
    2. On the New tab, enter a short description of the setting.
      For example: Limits active runs for PegaMKTSMS node type
    3. In the Owning Ruleset field, enter Pega-DecisionEngine.
    4. In the Setting Purpose field, enter dataflow/node_type/max_active_runs.
      where node_type is the case-sensitive name of the node type that is associated with the data flow service.
      For example: dataflow/PegaMKTSMS/max_active_runs
    5. Click Create and open.
  7. On the Settings tab, in the Value field, enter the limit for active runs that are allowed for the node type.
    Define the limit as a number greater than zero, for example, 10. You can use the special value –1 to indicate that the system can schedule an unlimited number of runs for the node type.
  8. Click Save.
    Note: After you change the dynamic system setting, it may take up to 5 minutes for the new limit to take effect.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us