Yeah, you’re not the only one GitHub-hosted runners have been kinda slow lately, especially on public repos. Sometimes it’s just a traffic spike on their end and jobs end up chilling in the queue way longer than usual.

It’s usually down to runner availability. GitHub scales runners pretty well, but during peak hours or heavy usage (like Mondays or big open-source events), things can lag.

A few things you can try:

If it happens a lot, consider setting up self-hosted runners — you get full control and no queue.

You can also try splitting your workflows into smaller jobs so they hit the queue separately and might run faster.

Keep an eye on GitHub Status — they do post when Actions are being weird.

But yeah, if the delay was random and it ran fine after, it's probably just GitHub being slow that day.

🕒 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! 💬

I recently set up ARM actions for my repo and it didn't even run once. All the tasks are stuck in queue or timed-out.

Is that even possible to get a queue?