Menu

31.7% of logged GitHub Agentic Workflows runs ended in failure: what 4.1 million archived runs show
📰

31.7% of logged GitHub Agentic Workflows runs ended in failure: what 4.1 million archived runs show

DEV Community: github·Piekwerk·4 days ago
#NKf4YBnD
#devtogithub#technology#devto#dev#agent
Reading 0:00
15s threshold

GitHub Agentic Workflows went generally available on October 28 , after a public preview that started in June. You write the automation as a Markdown file, the gh-aw compiler turns it into a standard GitHub Actions workflow, and a coding agent runs it on your existing runners with read-only defaults. A week after the general availability announcement, a research team published the first large-scale archive of what those workflows actually do in production. The headline number: 178,151 of 562,877 archived execution logs, or 31.7%, are linked to runs that ended with a failure conclusion.

If GitHub infrastructure is now absorbing agent traffic at this scale, this dataset is the closest thing we have to a flight recorder. GitHub itself has been retooling for it, and I wrote about the storage side of that push when 5,000 agents pushed 7,200 times a second inside GitHub's Rubicon .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.