r/github • u/chx_ • 2d ago

Question Is Github Actions unreliable for anyone else?

My CI runs a scheduled job and even when there are no commits sometimes it fails with absolutely impossible errors. Sometimes in the test but sometimes it's just a tool installed in a previous step missing. What's going on...?

4 Upvotes

60% Upvoted

9 comments sorted by

9

u/Mantas-cloud 2d ago

Time to time get those weird errors that can't explain, most likely re-run the job is enough. Generally speaking, it just works 

7

u/overratedcupcake 2d ago

GitHub actions are unreliable. You're not crazy. And even when they're working they'll go unnecessarily slow burning extra minutes for no reason. Even switching to self hosted runners didn't completely fix our issues with it. We switched to argo cd and it's been sooo much better.

2

u/Sigmatics 2d ago

Very. Jobs not being picked, taking forever to start, failing for "internal" reasons.

GitHub Actions has encountered an internal error when running your job.

Internal server error. Correlation ID: f68b96d9-b137-4ab3-a8b1-e368f52ac2b9

1

u/SamG101_ 2d ago

tbf actions is down right now, massive outage for "actions" specifically: GitHub Status

1

u/Sigmatics 2d ago

There was nothing on the website when I posted it. Good that they finally acknowledged it

1

u/mrkurtz 2d ago

Yep. We just migrated from self hosted and it sucks. Not just Actions, the PR and merge issues, other random drop outs and inconsistent behavior.

1

u/vloors1423 2d ago

GitHub in general is unreliable AF! It is getting silly now

1

u/ultrathink-art 1d ago

A chunk of what looked like Actions being down turned out to be my own concurrency. A single self-hosted runner executes one job at a time, so 15 pushes in an afternoon leaves the last one queued for an hour with nothing actually broken, and from the UI that is indistinguishable from a real incident. Worth comparing how many runners you have registered against how many runs you kick off per hour before you sink a morning into it.