Error tracking details is not working

Open
#39,494 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, react, typescript
Domain
frontend, observability

Research direction

Start from the Error Tracking view in the provided PostHog Cloud URL, reproduce the failure by opening a specific error name, and inspect the reported error and screenshot. Trace the detail-view entry point and determine why it fails. Done means an individual error opens its details successfully without the reported error.

Written by the indexing model from the issue text.

Description

bug
Bug Description

I got this error(see screenshot) when trrying to see error details

Image

URL: https://us.posthog.com/project/178440/error_tracking/0199bf97-0957-7f11-b88a-f8a93cddde44?timestamp=2025-10-07%2017%3A19%3A01.706000%2B00%3A00

How to reproduce

  1. Posthog panel (my project)
  2. sidebar meny click on Error Tracking - this view is working
  3. Click an specific error name to see more details - error is here

Additional context

Debug info
- [ X] PostHog Cloud, Debug information: [
Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/0199cecc-1ea6-7453-ac88-5736f31b84e0?t=2798
Admin: http://go/adminOrgUS/01975bd3-c093-0000-00ab-0d5dbe071df2 (project ID 178440)
]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.