GitHub-hosted ubuntu-latest runner not acquired — jobs cancelled after 15 minutes

[kingrabbit89]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Subject: GitHub Actions hosted runner not acquired for private repository
Hello,
I am experiencing a GitHub Actions runner provisioning issue on the following private repository:
Repository: kingrabbit89/robert-legal
Pull request: #21
Workflow: Robert Legal CI
Runner: ubuntu-latest
The workflow itself is valid and has successfully run many times before on the same repository.
For the current PR head:
55cc37aa7d44e0a1dae047855c98e6f35083068c
the jobs are created but no GitHub-hosted runner is ever assigned.
We observed the following three failed attempts:

• Run #112 (push)
  Run ID: 37359539609
• Run #113, attempt 1 (pull_request)
  Run ID: 37359548710
• Run #113, attempt 2 (pull_request)
  Run ID: 37359548710
  Each job remained queued for approximately 15 minutes and then terminated without ever starting any workflow step.
  GitHub’s check-run annotation explicitly states:
  The job was not acquired by Runner of type hosted even after multiple attempts
  The affected jobs had:
• no runner assigned;
• empty runner name;
• no executed steps;
• no job logs;
• API logs endpoint returning 404 / BlobNotFound.
  Approximate timing:
• #112: 18:54:54 UTC → 19:09:57 UTC
• #113 attempt 1: 18:54:59 UTC → 19:10:01 UTC
• #113 attempt 2: 19:12:11 UTC → 19:27:14 UTC
  Previous runs of the same workflow on the same day successfully acquired hosted runners within a few seconds.
  We have checked the repository configuration:
• GitHub Actions is enabled;
• the workflow is active;
• runs-on: ubuntu-latest;
• no custom runner group;
• no concurrency block;
• no environment approval;
• no job-level condition preventing dispatch;
• no timeout-minutes causing the queue;
• no pending deployments;
• PR is open and mergeable;
• no conflicting concurrent workflow run was found on the account during the affected period.
  The workflow file has not changed compared with earlier successful runs.
  The problem occurs before repository checkout or any project command is executed, so this does not appear to be caused by application code, tests, PostgreSQL, Prisma, or the CI commands themselves.
  The account/repository still shows available GitHub Actions usage, and GitHub-hosted Linux runner usage has been working normally earlier the same day.
  Could you please check whether there is:
• a hosted runner provisioning issue for this account/repository;
• a hidden account or billing restriction;
• a runner pool allocation problem;
• or any backend throttling / scheduling issue affecting ubuntu-latest?
  In particular, could you please confirm why these jobs could not be acquired by a hosted runner after multiple attempts?
  Thank you.

[kgeminicdev]

This matches an ongoing GitHub Actions incident rather than anything in your repository or account: Incident with Actions on githubstatus.com. It was opened at 19:11 UTC, and GitHub's 19:15 update describes "delays when assigning GitHub-hosted runners to Actions jobs" across runner configurations. Your first failures (18:54 UTC) started a little before it was posted, which is common, since incidents are often declared after the first reports.

I saw the same thing on a private repository of my own around the same time: the job sat in queued, never got a runner, and ended as cancelled with no steps run.

Since nothing ran, there's nothing to fix in the workflow. Once the incident shows as resolved, re-run the failed runs, either with "Re-run all jobs" on the run page or:

gh run rerun 37359548710

(and the same for 37359539609). You can subscribe to updates on the incident page to know when it's resolved. If jobs still aren't picked up after it's resolved, that would be the point to contact GitHub Support with these run IDs.