Unverified50% confidenceFactExact time
In the GitLab Jobs API, `commit SHA` points to the code version of this Job run, and if the retry occurs on the same commit it may be unchanged, so the same SHA does not mean it is the same Job.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn the GitLab Jobs API, `id` is the unique identifier of a Job, and a retry necessarily produces a new value, which is the most direct signal for judging stale references.69% similarUnverifiedIn the GitLab Jobs API, `finished_at` being null usually indicates that the Job is still running or has not yet started, and no conclusion should be drawn from this.64% similarUnverifiedIn GitLab CI/CD, when a Job fails and you click "Retry", GitLab generates an entirely new Job record for the same stage, with a new Job ID, a new trace, and new started_at/finished_at fields.61% similarUnverifiedawman uses Git's git worktree feature to implement isolated work trees, preventing conflicts when multiple agents modify code in parallel.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014356API
curl https://kongchang.com/api/v1/knowledge/claims/1014356MCP
get_claim(id=1014356)