BugMojoBugMojo
Get started
How-to

Inspect the network requests in a bug

Find the failed or slow request behind a bug, read its status, timing, and headers, and jump the replay to the moment it fired.

Applies toPlans:FreeProBusinessEnterpriseWhere:Web app

When a bug is really an API problem, the answer is usually one request. BugMojo captures the network activity from the session automatically, so you can jump straight to the failed or slow call, read its status, timing, and headers, and see what the user was doing when it fired.

Open the network panel

  1. Open the bug from your board, then select the Network tab on the bug detail page.

  2. Scan the request list. Each row shows the method, URL, status, time, size, and a waterfall bar, in the order the requests fired.

  3. Expand any row to see its request headers and response headers, with sensitive values masked.

Spot failed and slow requests

BugMojo flags requests that returned an error status or failed at the network layer. Use the failed filter to hide the noise and show only problem requests, narrow by method, or filter by URL. The time column and waterfall show how long each call took. Cross-reference the timing with the session replay to see what the user was doing when it fired.

Line a request up with the replay

  1. Click the request you care about. The replay jumps to the moment it fired.

  2. Watch what the user did just before and after the call, and check whether the page reacted to its status.

  3. To reproduce it outside BugMojo, rebuild the call from its method, URL, and headers, and add the body and fresh credentials yourself.

Common questions

Why is there no response body?

Bodies are never captured. They are dropped in the browser before upload, because that is where personal data and secrets usually live. You get the method, URL, status, timing, and masked headers instead.

Does the Network panel show request and response headers?

Yes. Expand any request to see its request headers and response headers. Sensitive values such as Authorization headers and cookies are masked in the browser before upload.

Can I replay a captured request to reproduce the bug?

Not from BugMojo directly. Use the method, URL, and headers shown for the request to rebuild the call in your own tool, and supply the body and fresh credentials yourself. Neither is captured.

Was this helpful?
Updated Jul 10, 2026 · Still stuck? Contact support

Related articles