# Review console and network details

Console and network evidence helps when the visible browser state does not fully explain a failure. Use these tabs to find JavaScript errors, failed requests, unexpected redirects, slow responses, and missing assets.

## Open console evidence

1. Open **Runs**.
2. Select a completed run.
3. Open the **Console** tab.
4. Use search, level, and source filters to narrow the list.

Console rows are useful for:

| Signal         | What it can explain                                                    |
| -------------- | ---------------------------------------------------------------------- |
| Errors         | JavaScript exceptions, failed client-side logic, or broken components. |
| Warnings       | Deprecations, blocked browser behavior, or suspicious runtime state.   |
| Logs           | App-specific debug output that explains what the page was doing.       |
| Source filters | Whether the message came from the app, browser, or another script.     |

## Open network evidence

1. Open the **Network** tab.
2. Search or filter by request type or content type.
3. Open a request row for details.

The Network tab can show request name, method, status, content type, duration, size, start time, route, and actions. The request details view can show request headers, response headers, response body, and image previews when available.

## What to look for

| Symptom                     | Evidence to check                                                      |
| --------------------------- | ---------------------------------------------------------------------- |
| Login failed                | Authentication requests, redirects, cookies, and 401 or 403 responses. |
| Data did not appear         | API responses, response bodies, and slow or failed requests.           |
| Page never stabilized       | Long requests, repeated polling, or console errors.                    |
| Button or form did not work | Console errors after the click or failed mutation requests.            |
| Asset missing               | 404 requests for scripts, images, CSS, or fonts.                       |

## Download response evidence

When a response body is available, the network details view can download it. This is useful for sharing an API response or attaching a failed request payload to a bug report.

## If console or network data is missing

Console and network tabs depend on run artifacts. If a tab is unavailable or empty, check whether the run is still finalizing, whether the selected configuration captures the needed evidence, and whether artifacts expired or were deleted.

For trace-level debugging, see [Open traces](/results/open-traces.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/results/review-console-and-network.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.