Skip to main content
A story is flaky when it doesn’t render the same way every time, for example because an animation is caught at a different frame or data loads in a different order. Flaky stories show up as changes that need review even when nothing about them changed. When flaky detection is enabled, OVR watches each story’s screenshots across recent builds on the main branch and marks a story as flaky when it:
  • keeps returning to a look it had before,
  • renders differently for the same commit, or
  • changes on most builds.
Flaky stories show a badge on their snapshot card on the build page and next to the status on the snapshot page. The badge reflects the story’s current history, so it also appears on older builds. To review only flaky snapshots, pick flaky in the flags filter on the build page. The same filter also offers warning for snapshots whose story threw an uncaught error while rendering.

​
Enabling detection

Flaky detection is off by default. An admin turns it on under Settings → Jobs, where they can also set how often stories are re-evaluated, as a cron pattern (7am and 7pm by default), and how many recent main-branch builds are considered (30 by default). Changes apply on the next scheduled run, without restarting the worker. Detection only uses main-branch builds captured after it was turned on, so it takes a few builds before stories can be flagged.