For when the pipeline turns green on retry and you just pretend you didn't see it.

When a job fails, Unflake tells you on the commit whether it has flaked before.

Sign in with GitHub See an example

Free during beta. No credit card.

Is it you, or is it flaky?

The answer is in the checks on the failing commit, when you need it.

Pull request · Checks
CI / test (ubuntu) Failing after 4m
Unflake This job has flaked before

CI › test (ubuntu) went green on retry 3 times in the last 7 days, last 2h ago.

A flake is the likelier explanation. It is not proof.

No history for the job? Unflake says nothing, so a quiet commit doesn't mean it's you.

And it keeps the record

Your tracker

One issue per flaky job

In GitHub Issues or Linear. It adds a comment each time the job flakes again.

Flaky: CI › e2e in acme/api

Slack

A daily digest

What flaked in the last 24 hours, most frequent first.

2 workflows went green on retry

Switchboard

The counts

Which jobs flake, how often, and which ones came back.

CI › e2e · 9 times in 30 days

What Unflake can see

Metadata about your runs. Never the contents.

Reads
Workflow run metadata. Job and step names. Run times.
Never reads
Logs. Test output. Environment variables. Source code.
Keeps
Flake details for 7 days. Daily counts for 90. Delete your account any time.
Permissions and limits

GitHub permissions: Actions (read), Checks (write), Metadata (read). Checks is only used for the note on a commit, and you can turn that off. If you turn on GitHub Issues, it also uses Issues (write) to open issues in the repo where a job flaked.

Unflake sees jobs and steps, not individual tests. It reports flakes; it doesn't retry or quarantine anything.

Read the privacy policy

Try it on one repo.

Install takes a minute. Remove it whenever you like.

Sign in with GitHub