Adding warning to Warehouse Selective Sync section #4772
Merged
Conversation
This file contains 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
|
Hi @pmbasco, @jacobwsmith19 - is there a permanent loss of data associated with a failed sync, or are you all able to recover the missing data with a backfill? If there's a potential for permanent data loss, I would recommend using the |
forstisabella
requested changes
Aug 21, 2023
forstisabella
approved these changes
Sep 7, 2023
|
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
Customers have reached out regarding failed warehouse syncs and after taking the proper troubleshooting steps we determine that the error is caused by the customer disabling the received_at property in one or many of their collections in their Warehouse Selective sync settings.
I think adding a warning that states that we use received_at as the sort key for all tables and that disabling this column will cause syncs to fail would be beneficial as it would avoid any failures / disruption in data flow.
Merge timing