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.
LinkedIn
Copied!

Table of Contents

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

The processing of a real-time data flow run failed with the following exception:

Failure threshold hit - too many errors occurred

Batch data flow runs always fail on encountering the first error.

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.

Error threshold message

Error threshold exception

Solution - Reduce the number of errors

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 flows.

Solution - Increase the threshold limit for data flow errors

You can increase the threshold limit for data flow run errors by completing the following steps:

  1. In the Explorer panel of Designer Studio, click Records > SysAdmin > Dynamic System Settings.
  2. In the Setting Purpose column, click the Filter icon.
  3. In the Search Text box, enter dataflow and click Apply.
  4. Click the dataflow/realtime/failureThreshold rule.
  5. On the Dynamic System Settings form, increase the threshold limit in the Value field.
  6. Click Save.
Did you find this content helpful?

100% found this useful


Related Content

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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