Suddenly github runners are taking too much time to kick start the pipeline

[arghasen93]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Run '....'
3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Runner Version and Platform

Version of your runner?

OS of the machine running the runner? ubuntu-latest

What's not working?

Our build pipeline is keep on waiting for the github runner at least for 10 minutes sometime also 20 minutes

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

[abhijeet-roy-polestar]

Facing same, where runners are not picking up builds with ubuntu-latest

[phracek]

See e.g. here https://github.com/sclorg/betka/actions/runs/15270059850/job/42943356222

I used ubuntu-latest. It does not work for GitHub organizations as well. Sometimes it took more than 3 hours.

[sebodnar]

experiencing same issue with self-hosted runners. tried version 2.235 and 2.234, our issue related with broker.actions.githubusercontent.com.
GET request to https://broker.actions.githubusercontent.com/message?sessionId=[edited]&status=Busy&runnerVersion=2.325.0&os=Linux&architecture=X64&disableUpdate=false has been cancelled
[2025-06-11 11:26:16Z ERR BrokerServer] System.IO.IOException: Unable to read data from the transport connection: Operation canceled. ---> System.Net.Sockets.SocketException (125): Operation canceled