> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Exceptions and issues – Error Tracking pocket guide

Canonical URL: https://posthog.com/learn/error-tracking/pocket-guide/101

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

Chapter 01

# Exceptions and issues – Error Tracking pocket guide

In an app like [Twig](https://twig.com), guests browse stays, pick their dates, book a stay, and then check the trip from their account. The engineers want to know when any part of that funnel breaks.

When something breaks, Twig's code throws an [exception](https://posthog.com/docs/error-tracking.md), such as a `TypeError`. Its [stack trace](https://posthog.com/docs/error-tracking/stack-traces.md) shows what led up to it.

To see them, the team uses PostHog Error Tracking. It captures each exception and its stack trace as a queryable event.

## Autocapture exceptions

The engineers run the Error Tracking Wizard on Twig. It installs PostHog and sets up source map uploads for Twig's bundle. Then they switch on [exception autocapture](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture) in the project settings.

Once the SDK loads, it captures uncaught exceptions in Twig.

For example, the **Trip details** button calls `readTripHost` without a `try`/`catch`. This error is uncaught, and the SDK catches it through `window.onerror`.

Click **Trip details** to see what it records:

Reset

twig

![Turquoise and pink buildings framed by palm trees](https://posthog.com/static/coast-7b4d656fded5753d13cc8c4accebeae1.jpg)

### Flamingo's Envy

Gold Coast, Queensland, Australia

**$240** / night USD