You can now build automations that react to individual test case changes the moment they happen, instead of waiting for the scheduled flakiness monitors to converge. Pick Test updated under When and tick the changes you care about — Marked as flaky, Unmarked as flaky, or state transitions to Enabled / Muted / Skipped — and the configured actions fire right away. The common shape: someone manually marks a flaky test, the automation immediately mutes it and pings Slack. Each automation-driven change also lands on the test case timeline attributed back to the rule that triggered it, so you can always see which automation moved a test and why.
