Called workflows cannot be queued onto self-hosted runners across organisations/enterprises. Failed to queue this job. Labels: 'ubuntu-latest' #25214
-
Reusable workflows being called from another repository are failing with the error in the title. This is the same problem as: 'ubuntu-latest' runner not found when using workflow_call between repositories - #16 by mohamed3114 There seems to be something to this reply, which mentions that this only happens when the concurrency limit is reached. When I retry the jobs with available capacity, they work, but every time there’s contention, these jobs fail now. It’s very disruptive and means I need to babysit my jobs so that I can re-submit the ones that use reusable workflows from another repository, once I can see that they won’t be queued. And in the meantime, I am getting emailed about these failed jobs too. I should add, there are NO self-hosted runners in use in my repository. cc @jenschelkopf (since you resolved the previous issue) |
Beta Was this translation helpful? Give feedback.
Replies: 17 comments 5 replies
-
Can anyone help with this? It’s so disruptive, every PR, commit, merge has these jobs that originate from reusable workflows failing and forcing me to watch and wait until there’s capacity before I re-run them… |
Beta Was this translation helpful? Give feedback.
-
Well this is my “me-too” post. You are absolutely right - it seems when a large number (~15-25 concurrent jobs) for a specific repo, this pops up. You are absolutely right that is very disruptive that my production pipeline fails because 2 people just pushed to feature branches. So much for velocity! |
Beta Was this translation helpful? Give feedback.
-
Don’t have much to add other than this is holding up a nifty new feature for our repos as well. |
Beta Was this translation helpful? Give feedback.
-
Adding my voice to the chorus here. Any idea when this bug will be addressed? |
Beta Was this translation helpful? Give feedback.
-
Thanks for reporting this; the team is investigating. I hope to have more to share soon. |
Beta Was this translation helpful? Give feedback.
-
Great to hear! Looking forward to a fix… 🙏 |
Beta Was this translation helpful? Give feedback.
-
3 days later and still no response. We have a Self-Hosted agent running with the tags required but GitHub actions is refusing to pick up and run it on the runner. This exact flow was working perfectly fine on a personal / private repo with exactly the same agent and machine. Only thing that has changed is that it is now an Organisation runner. Ok, re-read the original report and it notes that they are not using self-hosted runners, my bad. But issue persists |
Beta Was this translation helpful? Give feedback.
-
Yeah based on the error message it seems known/intentional that cross-org on self-hosted runners is not supported (though I have no idea why, that doesn’t seem intuitive at all); however this thread/topic is mainly to report that this error is newly, erroneously returned on GitHub runners. I recommend finding or starting a new topic to request a change in the functionality for cross-org self-hosted runners. |
Beta Was this translation helpful? Give feedback.
-
I have here 😃 |
Beta Was this translation helpful? Give feedback.
-
@ethomson any update?
Issues · actions/runnerThe Runner for GitHub Actions 🚀. Contribute to actions/runner development by creating an account on GitHub. Or is there any other way I can track progress on it? |
Beta Was this translation helpful? Give feedback.
-
@ethomson please can someone help? The problem is not only still occurring, it’s getting way worse. The jobs are now failing even more quickly, even when there are no other workflows running. They sit for a little over 1 minute and then die with the false self-hosted runner message, and all I can do is to keep trying over and over again and hope it runs.
empty
This experience is really awful. It’s killing my velocity and motivation to work on anything. Please help!! |
Beta Was this translation helpful? Give feedback.
-
@ethomson please, is there any update? |
Beta Was this translation helpful? Give feedback.
-
Hi Brian - I don’t have an ETA but I checked in with the engineering team and they believe they have identified the problem and occasions on which this occurs. They should be working on a fix now. Apologies for the delay. |
Beta Was this translation helpful? Give feedback.
-
Thanks @ethomson , did something change yesterday/today? I’m seeing one of these jobs properly queue without failing, so that’s hopeful… 🙏
Build software better, togetherGitHub is where people build software. More than 73 million people use GitHub to discover, fork, and contribute to over 200 million projects. |
Beta Was this translation helpful? Give feedback.
-
Yes, the fixes for this should be completely rolled out to all customers now. Thanks for letting us know that it’s working and thanks again for your patience. |
Beta Was this translation helpful? Give feedback.
-
Hi ethomson , seems like this is still occurring I’ve been facing it all day , here is my .yml file :
|
Beta Was this translation helpful? Give feedback.
-
This looks it might be a different issue. This thread is specifically about reusable workflows, your workflow is not a definition of a resuable workflow, and it is not consuming one either. You may be better served posting a new thread for this one. |
Beta Was this translation helpful? Give feedback.
Yes, the fixes for this should be completely rolled out to all customers now. Thanks for letting us know that it’s working and thanks again for your patience.