Anyone getting a Failed to queue workflow run. Please try again. error on workflow actions?

[jonrafila-aimai]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Anyone getting a Failed to queue workflow run. Please try again. error on workflow actions?

[mskrip]

Yes, as well as some workflow runs for particular workflows (even Github's CodeQL) being marked as This workflow run has been marked as disruptive. Even historically

[jonrafila-aimai]

Thanks, was concerned it was my action pipeline which was failing it. Guess we wait now.

[dozer75]

Not precisely answered? Just confirmed? 🤔

[publiux]

I am getting the same, and when building a docker image through the action, getting a 403 on my repo and being told my account is suspended.

[jonrafila-aimai]

Guess there's an issue with the service atm. Shouldn't be a big issue.

[sidhantsidd1251-dot]

dont worry be happy

[hastalavistababy]

Same

[sambeevors]

Yep - across all my actions

[jpalo]

Getting same error "Failed to queue workflow run. Please try again." No mentions of anything being disruptive nor that account would be suspended.

[WelshDev]

Yes, also getting "Failed to queue workflow run. Please try again."

[cfabriziohivemq]

+1, cannot even cancel them

[AnnaSasDev]

+1, on all organisations and personal repositories if I try and run actions.

[tinhlhm-fgs]

+1

[droideronline]

+1 stuck with this

[abszakacs]

+1

[yullai]

+1 : Failed to queue workflow run. Please try again.

[Tjitse-E]

It seems to be an active incident. See https://www.githubstatus.com/incidents/gnftqj9htp0g

[dozer75]

Yeah, finally they woke up...

[StephenHulme]

Worth noting that the same issue also presents as a ghost user on any PRs (and likely comments) that have been automatically created by the github-actions [bot].

[Isaaker]

+1 Failed to queue workflow run. Please try again.
Unable to update GitHub Pages websites because of workflows not running.

[GranTurismo]

+1

[weifish0]

me too. I am doing my univ hw. I also encountered this issue.

[weifish0]

BTW I am github pro user.

[0xmthan]

+1

[droideronline]

folks, its working when you try to run workflow from api/ gh cli. thats the workaround. thanks!

[SpenserCai]

Same here. Triggering the workflow from the GitHub UI fails with “Failed to queue workflow run. Please try again.”

The gh workflow run workaround did queue the workflow for me, but the run then failed during job setup while downloading an action archive from codeload.github.com:

“Failed to download archive ... after 1 attempts.”

So it looks like the issue may affect both workflow dispatch/queueing and parts of the Actions dependency download path.

[droideronline]

Same here. Triggering the workflow from the GitHub UI fails with “Failed to queue workflow run. Please try again.”

The gh workflow run workaround did queue the workflow for me, but the run then failed during job setup while downloading an action archive from codeload.github.com:

“Failed to download archive ... after 1 attempts.”

So it looks like the issue may affect both workflow dispatch/queueing and parts of the Actions dependency download path.

I am afraid so

[SpenserCai]

Same here. Triggering the workflow from the GitHub UI fails with “Failed to queue workflow run. Please try again.”
The gh workflow run workaround did queue the workflow for me, but the run then failed during job setup while downloading an action archive from codeload.github.com:
“Failed to download archive ... after 1 attempts.”
So it looks like the issue may affect both workflow dispatch/queueing and parts of the Actions dependency download path.

I am afraid so

It seems that the world is forced to stop releasing new versions today

[jonrafila-aimai]

seems to be somewhat working now.

[Isaaker]

Yes, now it allows to run the actions but recive your account is suspended.

[jonrafila-aimai]

Yes same here.

[samus-aran]

Hey folks! We have announced an incident with Actions and due to the incident we didn't have a public discussion created - so here is one manually created.

“This workflow run has been marked as disruptive” in the error reports does not reflect anything about your individual account. I hope that clarifies things.

[GranTurismo]

I ran my action. Problem is resolved for me

[jonrafila-aimai]

So the actions are now running but when creating releases I am getting Error: Sorry. Your account was suspended - https://docs.github.com/rest

[Isaaker]

Same here.

[jpalo]

Same here: HTTP 403: Sorry. Your account was suspended

[nebuk89]

Apologies this and being marked as 'distruptive' is a symptom of our current outage (the warning message and jobs not starting) we are actively working on this <3
(edited for clarity on disruptive message)

[jonrafila-aimai]

Seems like it could be fixed now.

[Isaaker]

Same here, actions are working again.

[nebuk89]

Yep we are coming back up, sorry for the alarming looking messages. They were a symptom here of a generic issue, this will be covered in the public RCA on this one.

Thank your for your patience as usual

[dozer75]

@nebuk89
As other mentions in this threads, runs that was started during the incident is not running + we can't cancel them... So, no the systems are NOT operational yet...

[GranTurismo]

Action running issue is completely resolved for me. It has been completed

[paulorgdigital]

Voltouuu

[munirahazari]

My queued pipeline has not yet run. What should We do ?

[EugeneGoroschenya]

My queued pipeline has not yet run. What should We do ?

+1

[Cancel run] leads to "Failed to cancel workflow."

[phatnh2301]

It can run new workflows normally, but cannot cancel old ones that are queued due to this issue.

[incrowdsports-connormacleod]

+1 for queued workflows being uncancelable.

[symeonmanis]

Has anyone found a workaround for the stuck queued runs? Any update from GitHub on when this will be fully resolved?

[mig5]

I still have a PR that was generated by github-actions[bot] that is visible in project boards, but 404s when you try to visit its URL. This has been the case since the Actions incident earlier this week. I cannot create a new PR from the same branch because 'Pull Request already exists'. No-one is replying to my support ticket.