Skip to main content


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

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.

Exceeded threshold for error count in real-time data flow run

Updated on March 11, 2021

The processing of a real-time data flow run failed with the following exception: Failure threshold hit - too many errors occurred.

Note: The processing of a real-time data flow run failed with the following exception: Failure threshold hit - too many errors occurred.

Cause

The number of errors encountered during the data flow run was greater than the threshold that was defined in the dataflow/realtime/failureThreshold Dynamic System Setting.

Solution: Reduce the number of errors

  1. Review the error details, stack traces, and log files to eliminate the root cause of each error. This way, you can ensure that the number of errors during a data flow run does not exceed the threshold limit.
    For more information, see Tips for troubleshooting data flow rules.

Solution: Increase the threshold limit for data flow errors

  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 box, enter dataflow, and then click Apply.
  5. Click the dataflow/realtime/failureThreshold rule.
  6. On the Dynamic System Settings form, increase the threshold limit in the Value field.
  7. Click Save.
  • Previous topic Data flow runs return errors while writing records to a database data set
  • Next topic No data flow service nodes are available

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.

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

Close Deprecation Notice
Contact us