Batch Job Step Exceptions
Batch job steps start a batch job either locally or on a different product environment.
Batch Job Step in Failed Status as a Result of a Batch Job Error
When a batch process (local or remote) ends with an error, the process step is automatically transitioned to Failed status.
In this case, you should:
-
Ascertain the cause of the job failure (in the local or remote environment).
-
If the issue is temporary or can be fixed, fix it and then rerun the batch job manually using the Batch Job Submission page (in the local or remote environment). If the resubmitted job ended successfully, you can transition the process step to the Completed status and use the Resume action at the process level to continue the process execution.
If the issue cannot be resolved, further investigation is required. In this case the process should remain in Stopped status.
Batch Job Step in In Progress Status While Batch Job Ended With an Error
When an Infrastructure Process Step that is associated with a batch job stays in In Progress status while the batch job ended with an error, further investigation is required. One possible cause for that situation could be an error that causes the job to fail and at the same time also prevents the job from communicating its status back to the originating process step.
In this case you should manually transition the step into Failed status and continue your investigation.