Skip to main content
LinkedIn
Copied!

Table of Contents

Tips for troubleshooting data flow rules

Version:

Only available versions of this content are shown in the dropdown

From the Data Flow landing page, you can access detailed reports on any errors that occur while a data flow is being processed. By analyzing these the error reports, you can quickly diagnose the root cause of an error.

Viewing error details

Each error message provides information about the data flow shape in which the error occurred and a link to a stack trace. You can review the method calls in the stack trace to understand the point at which your application encounters an error and which exceptions are raised.

  1. To view the stack trace, click Details in the error message.

    A data flow error message
    The message says that run failed because it exceeds the maximum
                                number of failed records, which is currently set to 1.
  2. Optional:

    To improve the readability of the stack trace, right-click inside the error window, and then click View page source.

Viewing the error count per component

You can view the number of failed records per component in a data flow to detect which shapes are the source of errors.

  1. In the header of Dev Studio, click Configure Decisioning Decisions Data Flows .

  2. Find the failed data flow, and click on its ID in the ID column.

  3. Click the Component statistics tab.

  4. In the #Failed records column, view the number of failed records that is displayed for the data flow component in which the errors occurred.

  5. View the error list per data flow component:

    1. In the #Failed records column, click the number of errors for a component.

      Number of failed records in the Component statistics tab
      The number of failed records for the Interaction History
                                        Outcome data flow is 5.
    2. Click View details to view the stack trace with an error.

      View details link
      The link is next to the thread has been recycled text in
                                        the top left corner of the section.
    3. Click View input record to view the record that caused an error.

      View input record link
      The link is under the data flow and node properties.

Viewing error count per node

You can view the number of partitions, which are equal segments of data that are spread across distinctive decision data nodes, that a data flow processes. In the case of an error, you can view on which node it occurred. You can also view the throughput per each node, which might give an indication as to which node is the slowest one.

  1. In the header of Dev Studio, click Configure Decisioning Decisions Data Flows .

  2. Find the failed data flow, and click on its ID in the ID column.

  3. On the Distribution details tab, view the data flow distribution details.

  4. View the error list per node:

    1. In the #Failures column, click the number of errors for a node.

      Distribution details tab
      The number of records processed for a node is 5, the number
                                        of failures is also 5.
    2. Click View details to view the stack trace with an error.

    3. Click View input record to view the record that caused an error.

Enabling debug logging

When error details do not give you enough information to fix an error, you can enable debug logging for the com.pega.dsm.dnode package to include more output in the generated log files. For example, you can view the SQL query that was running on an external database table when the error occurred.

  1. In the header of Dev Studio, click Configure System Operations Logs .

  2. On the Logs tab, click Logging level settings.

  3. In the Logger name field, press the Down Arrow key, and then select the name of a class that starts with com.pega.dsm.dnode or is in that package.

  4. In the Current level list, select the logging level.

    For more information, see Logging Level Settings tool.
    Selecting a logging level for decision management components
    The Logger Name field contains the name of a logger. The logging
                                level is error.
  5. Close the Logging level settings window dialog box to save your settings.

Related Content

Did you find this content helpful?

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