[May 2021] GitHub Actions has encountered an internal error when running your job

Hi There,

We are receiving this message “GitHub Actions has encountered an internal error when running your job.” across all of our CI builds across every repository in our organisation.

Github Status page is currently reporting no issues. Can someone from Github please look into this? This has started within the last hour.

3 Likes

Thanks for the post, my team is encountering the same issue. GitHubStatus is not updated with any info.

1 Like

Same issue on repos I work on.

2 Likes

Ditto. Earlier in the week, I’ve had a similar issue where workflows would fail to start and had to contact support to get it fixed. This is now twice in the same week. :frowning:

1 Like

Same issue today, worked fine yesterday.

1 Like

Same here, working fine yesterday.

1 Like

I’ve gotten a response from GitHub support:

Thank you for contacting GitHub Support.

This is caused by an ongoing incident. The team is currently working on it.

It has not been updated on our status page because we haven’t breached our thresholds yet for a status update.

I’ll give an update as soon as I can. Sorry for the inconvenience.

5 Likes

Thanks for the update, and yeah experiencing the same issue here!

1 Like

They should change their thresholds…

2 Likes

The status page now mentions an incident

1 Like

اذ قمت بلسحب يتم الرفض لماذ

1 Like

Today is the 3rd time in 2 weeks. What’s going on over at GitHub? :frowning:

3 Likes

Agreed, I’d love them to do a postmortem on the recent issues.

4 Likes

Today, my workflows are failing because actions/checkout@v2 says it can’t find my repository.

In case anyone else is having the same actions/checkout issues I’m having today, I managed to fix the problem by using a personal access token. Must be something wrong with the default authentication token obtained by the action. Anyway…

I changed:

- uses: actions/checkout@v2

To this:

- uses: actions/checkout@v2
  with:
    token: ${{ secrets.MY_TOKEN }}

Also, apologies for hijacking the thread for an unrelated error. :slight_smile: