Workflow's stuck and looping on build action, then suddenly crashed

[RubyRaven6]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Hello; a Github Action for the repo I'm working on seems to be stuck in Queueing despite there being an available Runner when I check the actions/runner page for CI for a build.yml.

When I go the action's page specifically, I see this:

Requested labels: ubuntu-latest
Job defined at: otohimexoxo/kawaii-expansion/.github/workflows/build.yml@refs/heads/master
Waiting for a runner to pick up this job...
Job is waiting for a hosted runner to come online.
Job is about to start running on the hosted runner: GitHub Actions 1000000044
Requested labels: ubuntu-latest
Job defined at: otohimexoxo/kawaii-expansion/.github/workflows/build.yml@refs/heads/master
Waiting for a runner to pick up this job...
Requested labels: ubuntu-latest
Job defined at: otohimexoxo/kawaii-expansion/.github/workflows/build.yml@refs/heads/master
Waiting for a runner to pick up this job...

What I gather from this is that it's essentially been looping for whatever reason.

Now, as I was writing this, the workflow cancelled itself, and gave this message:

If anyone can tell me what exactly happened, I'd be happy to know. Thank you!

[chess-king-dot]

Hey, @RubyRaven6
Yeah, this definitely looks like an issue on GitHub's side rather than anything wrong with your workflow config.

That "The job was not acquired by Runner of type hosted even after multiple attempts" error means GitHub Actions couldn’t assign your job to any available runner, even though it looked like one was queued.
It happens occasionally when there's high demand or temporary issues with GitHub’s hosted runners - especially if you're using ubuntu-latest.

The internal server error with a correlation ID also points to a backend hiccup.

If it’s still happening consistently:

Try re-running the workflow - sometimes it works fine on the second or third go.

You can also try temporarily switching the runner label to a specific version like ubuntu-22.04 just in case.

If it keeps happening, I’d suggest reporting it via GitHub support with the correlation ID - they can check logs on their end.

Hope that clears it up a bit!

[cattiesworld]

I have this too, I am on windows. I transferred my repo yesterday and now when I wanted to commit the update it started doing this. My repository is https://github.com/cattiesworld/CattiesWorld

[danasrequiem]

Seems like that repo has an active deployment. Did you find a work around?

[cattiesworld]

It appeared to have fixed itself as far as i can remember

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[alexey-sh]

For me it was out of disk space