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.

Reprocessing failed records in batch data flow runs

Updated on March 11, 2021

When a batch data flow run finishes with failures, you can identify all the records that failed during the run. After you fix all the issues that are related to the failed records, you can reprocess the failures to complete the run by resubmitting the partitions with failed records. This option saves time when your data flow run processes millions of records and you do not want to start the run from the beginning.

  1. Create a batch run for a selected data flow.
    For more information, see Creating a batch run for data flows.
  2. If the run fails, for example, due to an exceeded error threshold, click Continue.
    Result: The run completes with failures and lists failed record for that run.
  3. When the run finishes with failures, display details about each failed record by clicking the # Failed records column.
  4. Troubleshoot and fix the failures.
    For more information, see .
    Note: If you cannot fix the failures on your own, ask a strategy designer or a decision architect for help.
  5. In the batch data flow run, click Reprocess failures.
  6. Optional: To see how many partitions are resubmitted, click View affected partitions.
  7. To reprocess failures, click Submit.
    Note: When you reprocess failures, you resubmit all the partitions that contain failed records to reprocess all the records that are on these partition, whether the records failed or not during the run.

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