AgentSkillsCN

posthog-common-errors

诊断并修复PostHog常见错误和异常。 在遇到PostHog错误、调试失败请求或排查集成问题时使用。 可通过“posthog error”、“fix posthog”、“posthog not working”、“debug posthog”等短语触发。

SKILL.md
--- frontmatter
name: posthog-common-errors
description: |
  Diagnose and fix PostHog common errors and exceptions.
  Use when encountering PostHog errors, debugging failed requests,
  or troubleshooting integration issues.
  Trigger with phrases like "posthog error", "fix posthog",
  "posthog not working", "debug posthog".
allowed-tools: Read, Grep, Bash(curl:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>

PostHog Common Errors

Overview

Quick reference for the top 10 most common PostHog errors and their solutions.

Prerequisites

  • •PostHog SDK installed
  • •API credentials configured
  • •Access to error logs

Instructions

Step 1: Identify the Error

Check error message and code in your logs or console.

Step 2: Find Matching Error Below

Match your error to one of the documented cases.

Step 3: Apply Solution

Follow the solution steps for your specific error.

Output

  • •Identified error cause
  • •Applied fix
  • •Verified resolution

Error Handling

Authentication Failed

Error Message:

code
Authentication error: Invalid API key

Cause: API key is missing, expired, or invalid.

Solution:

bash
# Verify API key is set
echo $POSTHOG_API_KEY

Rate Limit Exceeded

Error Message:

code
Rate limit exceeded. Please retry after X seconds.

Cause: Too many requests in a short period.

Solution: Implement exponential backoff. See posthog-rate-limits skill.

Network Timeout

Error Message:

code
Request timeout after 30000ms

Cause: Network connectivity or server latency issues.

Solution:

typescript
// Increase timeout
const client = new Client({ timeout: 60000 });

Examples

Quick Diagnostic Commands

bash
# Check PostHog status
curl -s https://status.posthog.com

# Verify API connectivity
curl -I https://api.posthog.com

# Check local configuration
env | grep POSTHOG

Escalation Path

  1. •Collect evidence with posthog-debug-bundle
  2. •Check PostHog status page
  3. •Contact support with request ID

Resources

Next Steps

For comprehensive debugging, see posthog-debug-bundle.