Category: Automation

GitHub Actions: Job Stuck in Queued State

Read this guide in Polish

In the Actions job panel, it has a state ofqueued much longer than normal run. The cause may be inaccessible Runners, parallel limits or an active group of competitors.

How to determine the source of the error

Check availability of appropriate runners, account plan and minutes limits.

See if the previous workflow occupies the same group of competitors and when he finishes his work.

What to do step by step

1. Customize competitiveness to the scope of tasks; critical publications run consecutively without accidental cancel-in-progress. In particular, check whether the runs-on label corresponds to an online runner rather than a long-disabled runner.

2 . For self-hosted runner check online status and required labels.

How to check the score

Job starts after releasing resources, and the queue doesn't grow forever.

What to do

Do not remove all parallel limits for a process that saves to the same files.