| Changed selectors | A redesign, a markup change or an auto-generated id or class moves or renames the element a step points at. | The step's target no longer matches, so the element is never found and the step fails. |
|---|
| Timing and async loads | Content arrives from the network after the first render, and a single-page app can swap it in with no full page load. | A step runs before its element is ready, so the run passes on a fast load and fails on a slow one. |
|---|
| Dynamic content | Cookie banners, modals, personalization, ads and A/B-tested layouts differ from one visit to the next. | A step clicks the wrong element, or an overlay sits on top of the one it wanted. |
|---|
| Expired sessions | A saved sign-in times out, or a step meets a login wall it did not expect. | The run lands on the wrong page, and every step after it misses its target. |
|---|
| Environment differences | A different browser version, viewport, locale or set of input data is used than when the steps were built. | Steps that passed on one machine fail on another, or after a deploy, though the task never changed. |
|---|