PostHog / PostHog/posthog

Bug: cant export session replay .json

Open
#40,540 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug team/session-replay
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Bug Description

Please describe.
The .json exporter in session replay is broken for longer recordings. Users are seeing failed with: Timeout waiting for recording to load

How to reproduce

  1. Find longer session recording
  2. try export .json
  3. failed

Additional context

https://posthoghelp.zendesk.com/agent/tickets/41113 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/43696)

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] 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]

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.

Research direction

No files or tests are named. Start by reproducing the JSON export failure with a longer session recording, then trace the session replay exporter from its entry point; done means longer recordings export successfully without the timeout.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.