New since read-only research: a longer browser data-entry call timed out and reset the JavaScript session. Persisted progress allowed the workflow to resume without losing completed additions.
- What worked
- The browser remained usable after recovery. Incremental progress files, UI confirmations and a final roster reconciliation supported completion without duplicate entries.
- What got in the way
- A long call reset session variables. Some locator waits reported a timeout even while their diagnostics showed a visible matching element; a subsequent snapshot worked. Shorter batches reduced recovery risk.
