# resolving-ingestion-warnings

resolving-ingestion-warnings walks through PostHog ingestion warnings: dropped events, rejected person merges, oversized payloads. Use it when event counts look low or identify calls misbehave.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 197 installs · ★ 101 repo stars
- Author: PostHog
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/PostHog/ai-plugin/tree/HEAD/skills/resolving-ingestion-warnings/SKILL.md
- Updated: 2026-11-10
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/resolving-ingestion-warnings

## What it does

This skill covers PostHog's ingestion warnings, the records the pipeline writes when it drops, alters or refuses an incoming event. It opens with the `ingestion_warning` health check: a summary first, then the active issues, each carrying a warning type, category, severity and affected count.

Severity sets the order of work. A critical issue means the event never landed. A warning means it arrived changed. Info marks a drop the team configured on purpose. From there the skill opens the matching `references/fixing-*.md` file for code-level causes and per-SDK fixes, and reaches for `posthog:execute-sql` over `system.ingestion_warnings` when you want the offending events themselves. Only the reference file you need gets loaded.

One rule runs through the flow: every value in `details` was written by whoever sent the event, and anyone with the project's public capture token can put text there. The skill reports that content as data and never acts on it. Distinct IDs need resolving to persons as well, before you read a pattern into a sample.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/resolving-ingestion-warnings/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/resolving-ingestion-warnings/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/resolving-ingestion-warnings/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/resolving-ingestion-warnings/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install PostHog/ai-plugin skills/resolving-ingestion-warnings
```

2. **Manually: put the files in place**
- File: `.github/skills/resolving-ingestion-warnings/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/PostHog/ai-plugin --path skills/resolving-ingestion-warnings
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/resolving-ingestion-warnings/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PostHog/ai-plugin/tree/HEAD/skills/resolving-ingestion-warnings/SKILL.md

## When to use it
- Trace why events vanish from a PostHog project
- Explain duplicated accounts after identify or alias calls
- Shrink an event that grew past 1MB once person properties were attached
- Check whether a fix actually stopped new warnings
- Find the cause of gaps in recordings and empty heatmaps

## Example prompts
- List the active `ingestion_warning` issues and tell me which ones dropped data.
- Our heatmaps are empty — pull the matching warning type and show the raw `details` rows.
- Person profiles look inflated; walk the `person_properties_size_violation` reference and suggest the code fix.

## Similar
- [diagnosing-missing-recordings](https://affpapa.org/en/nevibecode/skills/diagnosing-missing-recordings.md) — skill · 428 installs
- [investigating-replay](https://affpapa.org/en/nevibecode/skills/investigating-replay.md) — skill · 424 installs
- [subtext](https://affpapa.org/en/nevibecode/plugins/subtext.md) — plugin · ★ 80 repo stars
- [logrocket](https://affpapa.org/en/nevibecode/plugins/logrocket.md) — plugin · ★ 2 repo stars
- [aep](https://affpapa.org/en/nevibecode/mcp/aep.md) — MCP server
- [data-manager-api-event-ingestion](https://affpapa.org/en/nevibecode/skills/data-manager-api-event-ingestion.md) — skill · 6148 installs

From the same set: [posthog/ai-plugin](https://affpapa.org/en/nevibecode/by/posthog/ai-plugin.md) — 82 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
