Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedactions/checkout 的作用是将仓库代码检出到 GitHub Actions 的 Runner 环境中72% 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.71% 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.66% 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.65% similarUnverifiedGitHub Actions原生的workflow_run触发器只能监听工作流完成事件，无法在同一工作流中阻塞等待另一个工作流的结果63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014360API
curl https://kongchang.com/api/v1/knowledge/claims/1014360MCP
get_claim(id=1014360)