Sep 2026 · 3 min read
Read the console and network log after a failed step
A red step is the start of the report, not the end. Console errors and the failing request usually explain it.
A timeout on a click usually means the control never became visible, not that Playwright is flaky. Open the console tab for the step first. Hydration errors, blocked scripts, and a failed analytics request are common noise — a 500 on the document or the API the button calls is the one to trust.
The network table is filtered by URL. Search for the path you expected, then check status and timing. A request that never left the page means the click did not run your handler. A request that returned 404 means the route itself is the bug.
Copy the console or network JSON from the report and paste it on the ticket. That is more useful than a second screenshot of the same blank state.