The correct response to a flaky test is never to retry or ignore it — always investigate the root cause. Common causes are race conditions in async flows, shared mutable test state, and environment instability. Quarantine flaky tests in a separate suite while they’re being fixed so they don’t block CI or silently drop from coverage.