A cached page.ai step could replay cleanly while the page did something else: it typed into the wrong row or picked the wrong option. These fixes come from a real customer application.
In a server-rendered list, a field's ID often carries its position, such as _3__Value. That position moves with the data. Recordings now anchor on the field's label, such as "Date of loss", so the step finds the right field on every record.
- Selectors that use the step's own environment value are tried first, then a stable ID
- A replay waits up to 10 seconds for a target that is in the page but not yet shown
- Every typing step confirms focus before it types
pressKeyno longer pressesEndbefore the key you asked for- Longer, named budgets for finding an element and checking it can be clicked