Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn 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.69% similarUnverifiedIn 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% similarUnverifiedGitHub Actions relies on backend databases to maintain task queues, runner allocation, workflow execution records, permission verification, and other states; a primary node failure prevented new tasks from being written to the scheduling queue, causing tasks to become stuck in a Queued state.68% similarUnverifiedWhen Factory polls GitHub to check for tasks, it uses ordinary code to call the GitHub REST API to check for label changes, consuming no tokens, and only launches agents when there is actual work to do.67% similarUnverifiedGitHub Actions 在定时执行方案中运行时间无限制，且支持重启后恢复和创建新会话67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014341API
curl https://kongchang.com/api/v1/knowledge/claims/1014341MCP
get_claim(id=1014341)