Skip to main content

ERROR TRACKING · INTERACTIVE DEMO

From browser error to a fix.

Explore a sample checkout error. See how repeat events stay in one issue and how a resolved error reopens when it comes back.

DEMO · sample dataExample Shop · production · release 1.4.2

TypeError: Cannot read properties of undefined

A shopper clicked “Place order”, but the checkout could not read the cart total.

Status
open
Occurrences
3
Regressions
0

Where it happened

submitOrder
src/checkout.ts:42:15

Uploaded source maps connect the production error to the original file and line.

Activity before the error

  1. Page opened · /cart
  2. Click · /cart
  3. Page opened · /checkout
  4. Click · /checkout

The collector records page URLs and click timestamps, without form values.

Issue activity

  • New issue → simulated alert

Try resolving the issue, then simulate another error. This example stays in your browser: it does not create project data or send notifications.

Create your workspaceOpen your projects

In your project, open Error tracking to connect your website and upload release source maps.