From d7ac6da0e1ce804f535e8859e7d1932fdd148e74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9CHeidi?= Date: Fri, 16 Jan 2026 10:14:43 -0500 Subject: [PATCH] fix-salt-explanation --- spec/job_batches_v2/job_batches_endpoints.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/job_batches_v2/job_batches_endpoints.yaml b/spec/job_batches_v2/job_batches_endpoints.yaml index 7af82478..8025207a 100644 --- a/spec/job_batches_v2/job_batches_endpoints.yaml +++ b/spec/job_batches_v2/job_batches_endpoints.yaml @@ -608,7 +608,7 @@ x-paths: **Job creation behavior** depends on the `mode` parameter: - **REUSE_EXISTING**: Returns an existing job if one matches the evaluated name template. If the matching job is - cancelled, deleted or closed, creates a new job with a unique name using the specified `salt` strategy. + closed, creates a new job with a unique name using the specified `salt` strategy. - **CREATE_NEW**: Attempts to create a new job with the evaluated name. If a job with that name already exists, appends a unique identifier using the specified `salt` strategy to ensure creation succeeds. @@ -1107,7 +1107,7 @@ components: **When salt is applied**: - - With **REUSE_EXISTING**: Salt is appended when an existing job with the evaluated name is in a closed or completed + - With **REUSE_EXISTING**: Salt is appended when an existing job with the evaluated name is in a closed state, ensuring a new unique job is created. - With **CREATE_NEW**: Salt is appended when a job with the evaluated name already exists, regardless of status.