diagnosing-missing-recordings
Diagnosing missing session recordings
When a user asks "why wasn't this session recorded?" or "why don't I have any recordings?", follow this workflow to systematically diagnose the cause.
Available tools
| Tool | Purpose |
|---|---|
posthog:execute-sql |
Query session event properties for diagnostic signals |
posthog:session-recording-get |
Check if a recording actually exists for the session |
posthog:query-session-recordings-list |
Search for recordings matching criteria |
Diagnostic signals
The PostHog SDK emits diagnostic properties on every event that explain the recording state. See the diagnostic signals reference for the full list.
The key signals are:
More from posthog/skills
posthog-debugger
Debug and inspect PostHog implementations on any website. Use this skill when a user wants to understand how PostHog is implemented on a page, troubleshoot tracking issues, verify configuration, check what events are being sent, or audit a PostHog setup. Works with Chrome DevTools MCP and Playwright MCP to inspect live websites.
106integration-nextjs-app-router
PostHog integration for Next.js App Router applications
100instrument-product-analytics
>-
90feature-flags-nextjs
PostHog feature flags for Next.js applications
88instrument-feature-flags
>-
86error-tracking-nextjs
PostHog error tracking for Next.js
85