Repository navigation
Document how warehouse connectors handle rows over event limits - #347
Merged
Merged
Conversation
Add a FAQ entry to the warehouse connectors page explaining what happens to rows that exceed Import API limits (oversized events, oversized values, events outside retention, future timestamps, unparseable timestamps) and whether each case shows up in Sync History. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NWx15JRnmXic8nvbVi6XMm
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 [Low impact] The PR appears safe to merge; the previous finding is addressed and no new actionable issue was found. Reviews (2) · Last reviewed commit: "Spell out string and list size limits in..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NWx15JRnmXic8nvbVi6XMm
kurbycchua
marked this pull request as ready for review
October 23, 2026 01:15
kurbycchua
enabled auto-merge (squash)
October 23, 2026 01:39
mherrman
approved these changes
Oct 23, 2026
This branch was successfully deployed
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.
Requested by Kurby Chua · Slack thread
Before: The warehouse connectors docs only covered events with timestamps in the future or before 1971. Nothing said what happens to rows that exceed Mixpanel's other event limits, such as oversized events or property values.
After: A new FAQ entry, "What happens to rows that exceed Mixpanel's event limits?", explains that connectors send events through the Import API and its limits apply. A short table lists each case (event over 1MB, oversized values, event older than the data retention period, event time more than 1 hour in the future, timestamp that can't be parsed), what happens to the row, and whether it shows in Sync History. The entry links to the existing limit docs rather than repeating the numbers.
How: One new
###entry at the end of the## FAQsection indocs/tracking-methods/warehouse-connectors.mdx, just before## Billing FAQ. No other lines changed.Notes for reviewers:
Generated by Claude Code