Bugwalk
Sign inFind out why

One failed checkout

Know why it broke.

Someone could not finish something in your product. Bugwalk shows why.

See what they did, what your app did, and the reason it failed. Every part of the answer can be checked.

Find out why

Card required. 3 days before you are billed.

ses_7f3a91production
Failed

  1. Signed in

    [email protected]

  2. Coupon

    SPRING-LEGACY

  3. Checkout

    POST /api/checkout500

src/checkout/total.ts
81export function applyDiscount(subtotal: number, coupon: Coupon) {
82  const discount = DISCOUNTS[coupon.code];
83 
84  return subtotal * (1 - discount.percentage / 100);
85}

Legacy coupon codes are not in the discount table

src/checkout/total.ts:84

01 /The problem

Someone got stuck. The error does not say why.

Bugwalk puts that story in one place.

  • 01

    The message says something failed. It does not say who got stuck, or why.

  • 02

    To find out why, you still look in three places: the logs, the page they were on, and the version that was live.

  • 03

    Each place shows one piece. None of them shows the whole story.

Before and after

Without Bugwalk

With Bugwalk

How it reads

Same failure. Two ways to see it.

One person could not finish paying. Here is what you see on your own, and what you see with Bugwalk.

Separate tools

Without Bugwalk

One visit

With Bugwalk

01

The error says something failed. It does not say who, which page, or what they tried.

Search their email. The failed payment is already on their visit.

02

The logs, the page, and the code are in different tools, and the times do not line up.

What they did, what your app did, and the error are in one place.

03

The code on your screen may not be the code that was live.

The answer names the file that was live, and the exact line.

02 /The user

Start with the person who got stuck.

  1. 01

    Search the email they already sent you.

  2. 02

    Find them once. After that, the visit stays under their name.

  3. 03

    You start with the person who got stuck, not with an error that has no name on it.

[email protected]
03 /The visit

See what happened around the failure.

[email protected] · checkout

  • 01

    What they did, the page they were on, and what your app did stay on one visit.

  • 02

    The error, and what your app wrote down, stay with that visit.

  • 03

    When someone says it did not work, you open their visit and see it.

04 /The investigation

You pick the failure. Bugwalk finds the reason.

Choose a visit that failed, or a group of the same failure, and run it. Bugwalk does not look at every error on its own.

  1. 01

    Rebuilds what happened

    Reads what that person did, and what your app did.

    TypeError reading ‘percentage’

  2. 02

    Finds the same failure

    Looks for other people who hit the same thing.

    38 in the last 24 hours

  3. 03

    Opens the live version

    Reads the version of your product that was running.

    src/checkout/total.ts

  4. 04

    Explains the reason

    Says what happened, why it happened, and where it broke.

    Legacy coupon codes are not in the discount table

  5. 05

    Shows the proof

    Every claim points at something that happened, or a line in your product.

    src/checkout/total.ts:84

Every claim points at something that happened, or a line in your product. If the proof is thin, the report says so.

Release [email protected]
  • src/checkout/orders.ts
  • src/checkout/total.ts
  • src/checkout/discounts.ts
05 /The deployed code

Look at the version that was actually live.

  • 01

    The failure remembers which version of your product was running.

  • 02

    Bugwalk opens that version, not the one you are editing now.

  • 03

    It can only read. It cannot change your code or your product.

[email protected]
06 /The change

An AI debug engineer fixes the code.

It writes the change and opens a pull request before you debug. You review the file and the line. Nothing merges until you say so.

  1. Read the visit

    What they did, and where it failed.

  2. Fix the code

    An AI debug engineer edits the line that failed, and nothing else.

  3. Open the pull request

    The request is ready before you debug.

  4. You review it

    You decide when it merges.

northwind/checkout

Skip a coupon the discount table does not know

src/checkout/total.ts

-  return subtotal * (1 - discount.percentage / 100);
+  if (!discount) return subtotal;
+  return subtotal * (1 - discount.percentage / 100);
  1. Read the visit
  2. Fix the code
  3. Open the pull request
  4. You review it

Looking it up

5 places

Logs · Requests · What they did · GitHub · The live version

Reviewing the request

Five places to check, then one request to review.

07 /The evidence

Check the answer. Do not just trust it.

Every finding points at what happened, or at a line in your product. If the proof is thin, the report says so.

Finding
08 /Issues

See who got stuck, not just the error.

Bugwalk groups the same failure, then shows who hit it, what they did, what broke, why, and where in your product.

Issues
AllOpenRegressedResolvedIgnored
09 /Inside a project

Six places. One product.

Overview

The last day: who showed up, what failed, and which visits just ended.

People

Search the email or id you already have. Open someone and read their visits.

Session

One visit: the pages, what they did, what your app did, and where it failed.

Issues

The same failure, grouped: who hit it, what they did, and why.

Investigation

A written answer: what happened, why, how sure it is, and what to change.

Project

How Bugwalk is connected to your product, what it may read, and your plan.

10 /Setup

Add it to your product. Then watch the next failure.

Connect your app and the code it runs, then ship. A visit shows what the person did, what your app did, and which version was live.

React, frontend:

$npx @bugwalk/wizard

Java, .NET, Ruby, and PHP

Point your existing OpenTelemetry agent at the Bugwalk OTLP endpoint. No Bugwalk library goes into those services at all.

$OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.bugwalk.dev
See the installation docs
11 /Privacy

It reads your product. Merging stays yours.

An investigation only looks. A qualifying report can open a pull request on a new branch, within the monthly allowance. It cannot push to the default branch, comment, merge, or write to your database. Passwords and card numbers are removed before anything leaves your app.

Dropped before anything is sent

Passwords, tokens, cookies, card numbers, authorization headers, and API keys are removed in your process. These rules cannot be turned off. Project, Privacy drops any other field names you list, and those values are not stored.

A branch, not the default

The GitHub App can pull the repositories you pick, run their tests, create one branch, and open a pull request. It cannot push to the default branch, comment, merge, or write to your database.

The SDK does not read

  • Keystrokes
  • Form values
  • localStorage
  • sessionStorage
  • IndexedDB
  • Environment variables
Read the privacy model
Before the batch leaves the app

Someone already told you where it broke.

Now find out why.

Find out why

Card required. 3 days before you are billed.

Pro is $39 · 3-day trial