Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen 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.68% 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.67% similarUnverifiedGitHub Actions原生的workflow_run触发器只能监听工作流完成事件，无法在同一工作流中阻塞等待另一个工作流的结果67% 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.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% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014358API
curl https://kongchang.com/api/v1/knowledge/claims/1014358MCP
get_claim(id=1014358)