Behavior when an exception occurs

The flow is not triggered.

The flow or subflow is not run.

The flow or subflow continues to run after the exception occurs. The run time is calculated from when the flow or subflow is first triggered until its status changes from Running to Exit or Done, or until the Overrun time is reached, whichever comes first.

The time is calculated from when the flow or subflow first starts running until its status changes from running to Exit or Done.

The job is not run.

The job is not run.

The job is still waiting. Submission of the job is retried until the configured number of retry times. If the job still cannot run, a Cannot Run exception is raised. The default number of retry times is 20.

The job continues to run after the exception occurs. The run time is calculated from when the job is successfully submitted until it reaches Exit or Done state, or until the Overrun time is reached, whichever comes first.

The time is calculated from when the job is successfully submitted until it reaches Exit or Done state.

The job array is not run.

The job array is not run.

The job array is still waiting. Submission of the job array is retried the configured number of retry times. If the job array still cannot be started, a Cannot Run exception is raised. The default number of retry times is 20.

The job array continues to run after the exception occurs. The run time is calculated from when the job array is successfully submitted until its status changes from Running to Exit or Done, or until the Overrun time is reached, whichever comes first.

Underrun

The time is calculated from when the job array is successfully submitted until each element in the array reaches Exit or Done state.