LinkedIn
Copied!

Table of Contents

Tips for troubleshooting data flow rules

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
    A data flow error message
  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. On the Data Flow landing page, find the failed data flow, and click on its ID in the ID column.
  2. Click the Component statistics tab.
  3. In the #Failed records column, view the number of failed records that is displayed for the data flow component in which the errors occurred.
  4. View the error list per data flow component by clicking the number of errors in the #Failed records column.
    Number of failed records in the Component statistics tab
    Number of failed records in the Component statistics tab
    1. Click View details to view the stack trace with an error.
      View details link
      View details link
    2. Click View input record to view the record that caused an error.
      View input record link
      View input record link

 

Viewing the 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. On the Data Flow landing page, find the failed data flow, and click on its ID in the ID column.
  2. On the Distribution details tab, view the data flow distribution details.
  3. View the error list per node:
    1. In the #Failures column, click the number of errors for the data flow component to view the list of errors.
    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.
Distribution details tab
Distribution details tab

 

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 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 (or is in the package) com.pega.dsm.dnode.
  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
    Selecting a logging level for decision management components
  5. Close the Logging level settings window dialog box to save your settings.

80% 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.