Automatic flake detection

Making your captures deterministic removes most flake at the source, but not all of it - a slow avatar, a sub-pixel reflow, or an animation frame can still slip through and come back as a change that is not real. UI Verify catches what is left by re-rendering, so a flaky diff never lands in your review as if it were a regression.

When a story comes back changed, UI Verify renders it again a few more times against the same commit. If those independent renders disagree with each other - same code, different pixels - the change cannot be a code change. It is a flake, and UI Verify marks the story flaky.

• It is auto-ignored. The story does not block the build and it is tucked into a collapsed section, out of your main review queue.
• It never becomes a baseline on its own. A flaky render can't quietly poison the next build's comparison.
• You stay in control. Open the collapsed section and deny it to force a failure, or accept it to bless it as the new baseline.
• It's billed as one snapshot no matter how many times it was re-rendered to prove it flaked.

No. A story is judged flaky per build, from that build's own renders - there is no sticky flake list. A story that flakes today and renders stably tomorrow returns to your normal review automatically, with nothing to clean up.

Detection is the safety net, not the fix. A story that flakes every build is telling you about real run-to-run variation - a clock, live data, an animation - and the cheaper fix is to remove it at capture time. See Fix flaky visual tests.

Flake detection is on by default. If you would rather see every change and triage each one yourself, you can turn it off per project in the project settings.