Update doc to reflect fixed unlocking behaviour

1915de0c · Albert Salim · c898fee2 · 1915de0c
--- a/doc/ci/pipelines/job_artifacts.md
+++ b/doc/ci/pipelines/job_artifacts.md
@@ -367,10 +367,20 @@ By default artifacts are always kept for successful pipelines for the most recen
 each ref. This means that the latest artifacts do not immediately expire according
 to the `expire_in` specification.

-If a pipeline for a new commit on the same ref completes successfully, the previous pipeline's
+When a pipeline for a new commit on the same ref completes successfully, the previous pipeline's
 artifacts are deleted according to the `expire_in` configuration. The artifacts
-of the new pipeline are kept automatically. If multiple pipelines run for the most
-recent commit on the ref, all artifacts are kept.
+of the new succesful pipeline are kept automatically. If multiple pipelines run for the most
+recent commit on the ref, the artifacts from the most recent successful pipeline are kept.
+
+When a pipeline for a new commit on the same ref fails, the previous pipeline's
+artifacts are deleted according to the `expire_in` configuration,
+with the exception of the artifacts from the most recent successful pipeline. The artifacts
+of the new failed pipeline are kept until a newer pipeline completes.
+
+When a pipeline for a new commit on the same ref is blocked, the previous pipeline's
+artifacts are deleted according to the `expire_in` configuration,
+with the exception of the artifacts from the most recent successful pipeline. The artifacts
+of the new blocked pipeline are kept until a newer pipeline completes.

 Keeping the latest artifacts can use a large amount of storage space in projects
 with a lot of jobs or large artifacts. If the latest artifacts are not needed in
@@ -384,10 +394,6 @@ a project, you can disable this behavior to save space:
 You can disable this behavior for all projects on a self-managed instance in the
 [instance's CI/CD settings](../../user/admin_area/settings/continuous_integration.md#keep-the-latest-artifacts-for-all-jobs-in-the-latest-successful-pipelines).

-When **Keep artifacts from most recent successful jobs** is enabled, artifacts are always kept for [blocked](../jobs/job_control.md#types-of-manual-jobs)
-pipelines. These artifacts expire only after the blocking job is triggered and the pipeline completes.
-For more information, see [issue 387087](https://gitlab.com/gitlab-org/gitlab/-/issues/387087).
-
 ## Troubleshooting

 ### Job does not retrieve certain artifacts