Hacker News Reader

Comment by plasma_beam | Hacker News Reader

For months now I've had scheduled GH Actions workflows that don't run on time, sometimes not at all. Like we're talking 4-8 hours later than the cron statement. Yesterday I finally gave up and just moved the trigger to AWS EventBridge Scheduler/Lambda. Maddening, but also we're talking code repos that are $0 for me. Not production level. I can't imagine people running Production pipelines on github.com.

View on HN

My scheduled for 8am PT GH actions workflows don't run until anywhere between 6-8 hours later. I gave up, and run them locally now. It is just to create a tag, and push to a specific place. A super simple problem that was solved for so long simply with GH Actions that just doesn't work anymore.

I've switched off to runners and event scheduling inside AWS, and am working on moving my company off of GitHub. I know engineers inside GitHub and it doesn't sound like the talk they've been putting out about reliability is actually being addressed with many resources internally; the best people in the company are chasing AI product features (which are apparently quite profitable).

At a previous gig we had a simple "reset staging" task on gha, that ran once a week on Tuesday

It ran fine for years, then around November just stopped and never ran again. Tried moving it around for which time it would trigger, and it just never started again. Opened a ticket, and got nowhere

Reply on news.ycombinator.com