Skip to main content

Table of Contents

Data flows cannot parse JSON records


Only available versions of this content are shown in the dropdown

The following exception occurs when you start processing a data flow run: Cannot parse JSON specific information about a data flow shape

The error message usually points at the Source shape of the Stream type in the data flow rule as the place where the error occurred.


This error is caused by incorrectly formatted JSON input records in the data set.


  1. Review the error details to find which shape in the data flow contains the incorrectly formatted JSON input records that caused the error.

    For more information, see Tips for troubleshooting data flow rules.
  2. Update the JSON formatting based on the root cause of the error.

    The following sample input record contains incorrectly formatted JSON:

      { "CellIdCaller": "1", "CallRecipient": "1", "CellIDRecipient": "1", "CallDirection": "1", "SubscriptionID": "S-892","TerminationCode": "1", "CallDuration": "20", "CDRMapping": {} "CallID": "1"

    The following sample error message identifies the root cause of the incorrect formatting:

    Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('"' (code 34): was expecting comma to separate OBJECT entries
    at [Source: com.pega.dsm.dnode.util.ClipboardPageJsonConverter$ByteBufferInputStream7158ccb7; line: 1, column: 185]

    Based on the above examples, you can conclude that the error is caused by a missing comma between the CDRMapping and CallID properties in the JSON input record.

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