From 9f4424f4fafa8da60b295e857f6aaf9e02616ac3 Mon Sep 17 00:00:00 2001 From: Mahmoud Ben Hassine Date: Thu, 5 May 2022 18:03:18 +0200 Subject: [PATCH] Fix documentation WRT restarting an abruptly stopped job Resolves #4037 --- spring-batch-docs/src/main/asciidoc/job.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/spring-batch-docs/src/main/asciidoc/job.adoc b/spring-batch-docs/src/main/asciidoc/job.adoc index e799f874da..2933332250 100644 --- a/spring-batch-docs/src/main/asciidoc/job.adoc +++ b/spring-batch-docs/src/main/asciidoc/job.adoc @@ -1821,5 +1821,4 @@ have to tell it manually that you know that the execution either failed or should be considered aborted (change its status to `FAILED` or `ABANDONED`). This is a business decision, and there is no way to automate it. Change the -status to `FAILED` only if it is not restartable or if -you know the restart data is not valid. +status to `FAILED` only if it is restartable and you know that the restart data is valid.