# Stuck on Red? Understanding GitHub Actions Failing Streaks

DevFeed: [Stuck on Red? Understanding GitHub Actions Failing Streaks](<https://devfeed.tech/articles/stuck-on-red-understanding-github-actions-failing-streaks-112683.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.41863>)

Author: Aref Talebzadeh Bardsiri (UMONS), Tom Mens (UMONS), Alexandre Decan (UMONS), Thomas Degueule (LaBRI), Jean-R\\'emy Falleri (LaBRI)

Published: 2026-11-02T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [failure](<https://devfeed.tech/tags/failure.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [network](<https://devfeed.tech/tags/network.md>), [repository](<https://devfeed.tech/tags/repository.md>), [service](<https://devfeed.tech/tags/service.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

Across 30.9 million GitHub Actions runs from 154,000+ workflows, failures commonly persist in streaks: three quarters of failing runs follow another failure, and half of workflows with at least three runs have a streak. Multi-purpose workflows have streaks more often, even at the same size. Although most streaks end within hours, the one in five lasting over a day account for most time spent failing. Repository changes do not explain every transition: a third of streaks start and two fifths end without a change; in a sample of 100, those ending without a change most often involved network problems or external services. The findings caution maintainers against attributing failures automatically to the latest commit, and suggest flagging unchanged-repository failures and alerting maintainers when a workflow remains failing for more than a day.

## Source excerpt

arXiv:2610.41863v1 Announce Type: new Abstract: GitHub Actions is the de facto CI/CD service for GitHub repositories. Its workflows should not fail when they are not expected to, nor keep on failing too long. We empirically study failing streaks, i.e., uninterrupted series of failing runs of a workflow, in 30.9M+ runs of 154K+ workflows of 43K+ GitHub repositories over 238 days. We study how failing streaks begin and end, and what happens during them, based on the trigger and the commit of each run. We also classify all workflows by their purposes, such as building, testing or deploying, and we inspect the logs of a small sample of failing streaks. Failing runs mostly come in streaks: three quarters of them follow another failing run, and half of the workflows with at least three runs have at least one failing streak. Workflows serving multiple purposes have failing streaks more often, even at the same size. Most failing streaks end within hours, but the one in five that last more than a day account for the lion's share of the time that workflows spend failing. A third of the failing streaks start, and two in five end, without any change to the repository. In a sample of 100 failing streaks, those that end this way most often fail because of network issues or an external service. These findings suggest that maintainers should not assume that a failure comes from the last commit. GitHub and tool builders could flag failures that occur without any change to the repository, and alert the active maintainers when a workflow stays failing for more than a day.