diagnosing-missing-recordings

Diagnose missing session recordings using PostHog diagnostic signals and decision trees.

58|5|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/PostHog/skills --skill diagnosing-missing-recordings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-missing-recordings
Source: https://github.com/PostHog/skills/tree/main/skills/omnibus/diagnosing-missing-recordings
Command: npx skills add https://github.com/PostHog/skills --skill diagnosing-missing-recordings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses why a session recording is missing or was not captured, guiding users through a systematic workflow to pinpoint the root cause.

Core Features & Use Cases

  • Diagnostic signals: interprets SDK properties such as recording status, start reason, trigger statuses, and buffering metrics to determine why a recording was not captured.
  • Per-session diagnostics: checks if a recording exists for a given session, queries diagnostic data, and applies the diagnosis logic to surface actionable verdicts.
  • Guidance for remediation: pairs verdicts (e.g., DISABLED, AD_BLOCKED, TRIGGER_PENDING, SAMPLED_OUT, BUFFERING_EMPTY, PAUSED, FLUSH_BLOCKED) with concrete next steps.

Quick Start

Provide a session ID to run through the diagnostic workflow and surface the most likely cause and remediation steps.

Frequently Asked Questions about diagnosing-missing-recordings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my PostHog session recordings missing or not captured?

Missing session recordings can occur because they are disabled, ad-blocked, sampled out, or paused. Evaluating diagnostic signals and trigger statuses against project settings identifies the root cause.

How do I diagnose a missing PostHog session recording?

Provide a session ID to retrieve diagnostic signals and verify recording statuses using query tools. Apply diagnosis logic to return a verdict like CAPTURED or BUFFERING_EMPTY with remediation steps.

What diagnostic signals indicate a session recording was not captured?

Diagnostic signals include recording status, start reason, trigger statuses, and buffering metrics. Interpreting these SDK properties determines whether the recording was disabled, blocked, or pending.

Can I check why a specific session recording failed in PostHog?

Yes, per-session diagnostics checks if a recording exists for a given session. Querying diagnostic data and applying diagnosis logic surfaces actionable verdicts to guide remediation.

What should I do if a session recording verdict says FLUSH_BLOCKED or SAMPLED_OUT?

When a session recording verdict is FLUSH_BLOCKED or SAMPLED_OUT, follow the provided concrete next steps. Remediation guidance pairs each specific verdict with actions to resolve the capture issue.