-
Notifications
You must be signed in to change notification settings - Fork 366
Automatic retry docs #7314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Automatic retry docs #7314
Conversation
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
pwseg
reviewed
Dec 11, 2024
pwseg
previously approved these changes
Dec 11, 2024
Co-authored-by: pwseg <[email protected]>
## Automatic retry handling | ||
|
||
> info "Automatic retry handling feature might not yet be available in your workspace" | ||
> To ensure overall system stability and performance, Segment is releasing automatic retry handling to all workspaces in a phased rollout program. Segment expects this feature to be available to all customers by January 31, 2025. | ||
|
||
Segment automatically retries events that were extracted from your data warehouse but failed to load for up to 14 days or 5 syncs following a partially successful sync or a sync failure. | ||
|
||
Segment checks for the latest changes in your data before loading the failed records on a subsequent (automatically scheduled or manually triggered) sync to ensure the data loaded into Segment isn’t stale and only the latest version of the data is loaded to destination. If the error causing the load failure is coming from an upstream tool, you can fix the error in the upstream tool to resolve the load error on a subsequent sync. | ||
|
||
> warning "Syncs with intervals less than one hour may not see failed events on the sync immediately following failed record" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one hour -> two hour
Syncs with intervals less than two hour.
intervals less than or equal to two hour
pwseg
previously approved these changes
Dec 11, 2024
forstisabella
commented
Dec 11, 2024
forstisabella
commented
Dec 11, 2024
pwseg
approved these changes
Dec 12, 2024
bharathboregowda
approved these changes
Dec 12, 2024
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
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.
Proposed changes
Added docs for automatic retry at request of one of the RETL engineers
Merge timing
soon - pending ENG approval
Related issues (optional)
#6612 #7035