Skip to main content


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

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.

Review the lifecycle events of data flow runs (8.2)

Updated on September 10, 2021

Limit data flow run downtime and troubleshoot issues effectively by generating and reviewing a report on the lifecycle of data flow runs. If a run fails, you can generate an extensive lifecycle report with a single click and analyze the details of the failure event to quickly pinpoint the cause and restore the run. For example:

Thumbnail

Sample data flow run report 

The following example is a JSON document that constitutes one of the Event details sections of the report:

{"type":".PartitionStatusTransitionMessage",
"senderNodeId":"prpc",
"timestamp":1546597138260,
"runId":"DF-1",
"originator":"MultiplePartitionExecution",
"reason":"Encountered error while processing run: Severe exception in stage: Three Dropped Calls",
"oldStatus":"IN_PROGRESS",
"newStatus":"FAILED",
"partitionIds":["19"]}

In the report, filter and summarize the records to highlight relevant data and transform the report into a clearer and more digestible form. If you require assistance with debugging an issue, you can export the report to a .pdf or .xls file and share it with Global Customer Support (GCS).

For more information about accessing event details, see Creating a real-time run for data flows and Creating a batch run for data flows.

 

  • Previous topic Interpret the decision funnel with simulation tests (8.2)
  • Next topic Optimize decision strategy performance (8.2)

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us