Unverified50% confidenceFactExact time
In the GitLab Jobs API, `pipeline ID` usually remains unchanged when retrying a Job within the same Pipeline, so it is more used to distinguish "cross-pipeline" scenarios.
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.66% similarUnverifiedGitHub Actions原生的workflow_run触发器只能监听工作流完成事件，无法在同一工作流中阻塞等待另一个工作流的结果63% 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.62% similarUnverifiedUnlike code-completion tools such as GitHub Copilot, Bolt targets the scenario of going from nothing to a runnable application, rather than providing localized assistance within an existing codebase.62% 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.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014357API
curl https://kongchang.com/api/v1/knowledge/claims/1014357MCP
get_claim(id=1014357)