Skip to main content

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

Data flows cannot parse JSON records

Updated on May 17, 2024

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

Note: 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 Investigating data flow run failures.
  2. Update the JSON formatting based on the root cause of the error.
    For example:

    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.

  • Previous topic Investigating data flow run failures
  • Next topic Data flow fails to run from a job scheduler in the System Runtime Context

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us