This would definitely come in handy for situations where the failure is very likely to be transient. For instance, we run a link checker, and that will fail during brief outages of the websites we are linking to.

We have some custom bash logic to retry our test suite when it fails. However, retrying the test suite is _slow_, as you would imagine. I would love greater visibility into transient failures without failing people's builds, so that they can be investigated.

Would also like to see this implemented. Any updates here?

I think what most of us are looking for is essentially being able to automatically execute “Rerun Workflow From Failed” n times when a job fails.

It's easy enough to retry a step with some basic bash logic, however, particularly when running integration tests we occasionally run into transient memory issues that require the job itself to be rerun in a new container. This cannot be achieved via bash or orbs to my best knowledge.

I know that it's possible to retry an entire pipeline by making an API call to CircleCI when: on_fail but that is wasteful when only 1 or 2 jobs are failing in a workflow consisting of dozens of jobs.

Any update on this? Folks have been asking for it in your forums since 2017. Other CI systems have this out of the box. We really don't like having to manually hit the retry button every time a build fails due to external issues...

I need something like this feature in Gitlab CI https://docs.gitlab.com/ee/ci/yaml/#retry when a job fails, the job will retry.

Thanks for that feedback Tyler. I'm curious, would it be acceptable to use an orb in order to emulate the retry logic?

Yes please! In a perfect world, a build failure would always represent a need for a code change, but the reality is that many build scripts have issues that just are a bit flaky. More often than not, we end up having to make arbitrary code changes and push just to try again :(