What’s captured
- Web
- iOS
Full request list for the page under test:
GET/POST/etc., URL, status, resource type (document, xhr, script, image, …), duration, and response size. Failed requests (DNS, abort, CORS) appear with status: 0 and an error string.Fields
Each captured request includes:
If a run makes a very large number of requests, the oldest are dropped and the artifact is flagged as truncated.
Accessing captured traffic
- Run page — open a completed run and scroll to the Network section.
- API — fetch a run and read
network_log_url(JSONL, one request per line). See Runs API.
Reading network logs in a flow
To assert on traffic mid-flow, use the Read Network Logs action — e.g. “Read the network logs and verify thePOST to /api/login returned 200.” See Flows.