-
I received the following error:
Any idea what it means? Looks like no steps of my workflow even tried to run. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments
-
Saw same issue, and now seeing:
|
Beta Was this translation helpful? Give feedback.
-
Seeing the exact same here as well. I’m thinking there’s something wrong in the GitHub Actions infrastructure at the moment. |
Beta Was this translation helpful? Give feedback.
-
Same issue for me with 2 repositories (managed runner and self-hosted runner). |
Beta Was this translation helpful? Give feedback.
-
Seeing the same issue here as well. I take it to mean that it GitHub is unable to create the host the actions will run on. Nothing has changed in our action configuration, so I second/third/fourth/fifth the idea that Actions are broken. |
Beta Was this translation helpful? Give feedback.
-
I am getting the same error as “This Check failed” for any github action triggered |
Beta Was this translation helpful? Give feedback.
-
My action runs every hour on the hour, this time I got:
If everybody else is having issues too I guess the problems are on GitHub’s end. However, their status page is showing everything is ok. |
Beta Was this translation helpful? Give feedback.
-
I was just able to get an action to run. |
Beta Was this translation helpful? Give feedback.
-
Same, it’s back for the moment. |
Beta Was this translation helpful? Give feedback.
-
Apologies - this is an internal GitHub error message. We were rolling out a new deployment that had errors for some workflows, and I’m afraid that yours was one of the workflows affected. We’ve rolled that deployment back - if you run your workflow now, the problem should be resolved. Apologies for the inconvenience! |
Beta Was this translation helpful? Give feedback.
-
It seems this is happenning again for last half an hour or so but I dont see it on https://www.githubstatus.com/ |
Beta Was this translation helpful? Give feedback.
Apologies - this is an internal GitHub error message. We were rolling out a new deployment that had errors for some workflows, and I’m afraid that yours was one of the workflows affected.
We’ve rolled that deployment back - if you run your workflow now, the problem should be resolved. Apologies for the inconvenience!