Persistence

Overview

The execution engine records internal tracking data that includes the state information associated with a running workflow instance. The execution engine persists the workflow instance state when a subprocess completes. The persisted state can be used to recover and restart a workflow instance from failure conditions, or if it was stopped. If a workflow is stopped normally, the postsubprocess, postprocess, and unload steps run before the instance stops (they will not run if the server crashes). The workflow instance can continue from the start of the current subprocess by using the restart command. When this happens, the instance restarts by running the load, preprocess, and presubprocess steps. Then it restarts at the beginning of the subprocess that was running before the workflow stopped.

You can significantly improve the performance of your workflows by implementing one or all of the following recommendations:

• Decrease Persistence Points
• Reduce Acticities
• Enable Persistence
• Disable Persistence