TOF-446: Add per-error troubleshooting pages for top Mixpanel API errors - #179
Draft
tylergoerzen-mxp with Copilot wants to merge 3 commits into
Draft
TOF-446: Add per-error troubleshooting pages for top Mixpanel API errors#179tylergoerzen-mxp with Copilot wants to merge 3 commits into
tylergoerzen-mxp with Copilot wants to merge 3 commits into
Conversation
Co-authored-by: tylergoerzen-mxp <259741734+tylergoerzen-mxp@users.noreply.github.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Copilot
AI
changed the title
[WIP] Create per-error troubleshooting pages for top verified error strings
TOF-446: Add per-error troubleshooting pages for top Mixpanel API errors
Aug 18, 2026
Contributor
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| docs.json | Adds the five troubleshooting pages under a dedicated FAQs navigation group. |
| troubleshooting/errors/400-bad-request.mdx | Documents validation failures and correctly explains partial success for strict imports. |
| troubleshooting/errors/401-unauthorized.mdx | Documents credential and regional-endpoint authentication failures. |
| troubleshooting/errors/403-forbidden.mdx | Explains forbidden ingestion responses and recommended diagnostic steps. |
| troubleshooting/errors/413-payload-too-large.mdx | Documents request, event, and batch size limits. |
| troubleshooting/errors/429-rate-limit-exceeded.mdx | Documents the corrected rolling ingestion limit and exponential-backoff guidance. |
Reviews (2): Last reviewed commit: "Rewrite the error pages against the Open..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
The original pages documented behavior Mixpanel's API does not have. Rewritten from openapi/ingestion.openapi.yaml and reference/import-events.mdx. Corrected: - Rate limit was "2GB per hour". It is 2GB of uncompressed JSON per minute, or ~30k events/sec on a rolling one-minute basis. The old figure would have made anyone throttle a backfill 60x too slowly. - All five example bodies used "code": 0. Real responses return the HTTP status as code plus a status string; /import 400s also carry num_records_imported and per-record insert_id. - The 429 page told readers to respect a Retry-After header. Mixpanel does not send one. The page now says so and gives the documented backoff: start 2s, double to 60s, 1-5s jitter. - /import request limit was 2MB. It is 10MB uncompressed. - Gzip was described as a way to avoid 413s. The limit is measured against the uncompressed body. - Empty distinct_id was listed as a 400 cause. The docs instruct you to send an empty string for unattributed events; what is rejected is the placeholder list (anon, null, n/a, and so on). - "Retry the batch one event at a time" contradicted the reference, which says not to retry 400s at all. Removed: - The 403 page described /import, which never returns 403 (the spec declares 200, 400, 401, 413, 429). Rescoped to /track, /engage, and /groups, which do, using the spec's ErrorResponse shape. - An invented permission table using the org role "Member" for a project-level operation, and a nonexistent "user profiles are disabled" project setting. Added the /track 5-day historical window, a common reason backfilled events never appear. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Creates dedicated AEO-optimized troubleshooting pages for the most common Mixpanel ingestion API errors, enabling search engines and AI answer engines to surface targeted fixes for specific error codes.
New pages (
troubleshooting/errors/)distinct_id, wrong project token, malformed JSON, invalid timestamps, oversized property namesRetry-After-aware exponential backoff implementationNavigation
Restructured the FAQs tab in
docs.jsonfrom a flatpageslist to agroupslayout, adding a new "Error Troubleshooting" group alongside the existing FAQs group.