internal_error
internal_error
Section titled “internal_error”HTTP status: 500 Internal Server Error
How to fix
Section titled “How to fix”- Retry the request. Many 500s are transient — a deploy lap, a connection-pool blip, a one-off DB timeout. Retry once after 5 seconds before deeper investigation.
- Check our status page for ongoing incidents.
- For repeated 500s on the same endpoint, file a support ticket immediately. We've been notified via
$exceptioncapture, but a customer report accelerates triage with the actual user-visible impact. - Don't blame the request body. 500 means our code failed; it's not a hint that your input is wrong. If the input were wrong, you'd see
invalid_inputor a more specific 4xx.
What this means
Section titled “What this means”A bug or unexpected condition in our service caused the request to fail. Our PostHog $exception capture already has the full stack trace and your request_id; we don't need you to forward error details. The static message stays generic by design (per our CLAUDE.md rule: never leak err.message to clients).
Related errors
Section titled “Related errors”service_unavailable— our infrastructure briefly down (not a bug)provider_unavailable— upstream scraping provider failed
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll find the exact stack trace in our logs.