...
Must change the Mode property of all the checkpoints used in the process flow to Rerun. For information on how to add a checkpoint, refer to Using Actions in Process Flow.
Following are the major subsections:
...
...
...
How does Rerun Works?
During execution of a process flow, at every checkpoint, the Process Flow stores its current state in a rerun file. There is one rerun file for each execution of a process flow. These rerun files are stored in a rerun folder defined in the property abpm.reprocessing.repository.root.
If the process flow aborts, the rerun file will have the state of the process flow till the last checkpoint. If no checkpoint is reached, no rerun file is created and the process flow can never be reprocessed after failure. In the rerun file, only the state of the process flow is stored. Intermediate data of the process flows are stored in the repository folder. If your process flow has checkpoints, and the rerun is enabled, then when you rerun, the Kernel looks for the rerun file for that particular process flow instance. If it finds such file, it picks up the intermediate data from there and resumes the process flow from last checkpoint state.
The rerun file remains in the rerun folder unless the process flow execution is completed successfully. The Intermediate data gets deleted automatically by Data Cleanup or a user can delete it manually to free disk space. To know more about data cleanup, refer to the section Data Cleanup.
Enabling Rerun
Perform the following steps to enable rerun:
- In your process flow, select each of your check points one by one.
- Change their respective Mode property to Rerun. This enables the rerun feature.