Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn the GitLab Jobs API, the `runner` field records the Runner that actually executed the Job and its tags, and is field-level evidence for identifying the "free server instead of Runner" misconception.71% similarUnverifiedIn GitLab CI/CD, a Job is the smallest execution unit, bound to an auto-incrementing numeric Job ID, and has its own trace log and status fields.71% 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.69% similarUnverifiedIn 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.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014354API
curl https://kongchang.com/api/v1/knowledge/claims/1014354MCP
get_claim(id=1014354)