posthog-common-errors
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".
When & Why to Use This Skill
The PostHog Common Errors skill is a specialized diagnostic tool designed to streamline the troubleshooting process for developers and data engineers. It provides instant identification and actionable fixes for the most frequent PostHog integration issues, including authentication failures, rate limiting, and network timeouts, ensuring reliable data collection and minimal downtime.
Use Cases
- Case 1: Resolving 'Invalid API key' errors during initial SDK setup by verifying environment variables and credentials.
- Case 2: Handling 'Rate limit exceeded' exceptions by implementing recommended exponential backoff strategies to maintain data flow.
- Case 3: Diagnosing network latency and timeout issues using automated connectivity checks to PostHog API endpoints.
- Case 4: Verifying local system configurations and service status via CLI commands to ensure the integration environment is healthy.
| name | posthog-common-errors |
|---|---|
| description | | |
| 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:
Authentication error: Invalid API key
Cause: API key is missing, expired, or invalid.
Solution:
# Verify API key is set
echo $POSTHOG_API_KEY
Rate Limit Exceeded
Error Message:
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:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
// Increase timeout
const client = new Client({ timeout: 60000 });
Examples
Quick Diagnostic Commands
# 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
- Collect evidence with
posthog-debug-bundle - Check PostHog status page
- Contact support with request ID
Resources
Next Steps
For comprehensive debugging, see posthog-debug-bundle.