Add faq that retries could account for events not filtered by Destination Filter #5223
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
…Destination Filter Customer are confused that sometimes they are still seeing events flowing through after adding Destination Filter. Added the following faq to indicate that retries could account for these events not filtered by Destination Filter "Why do I see events being sent through after I just added a destination filter? If Event Delivery page shows events have been retried, the retries could account for events that did not get filtered when the Destination Filter is just added. Such scenario can occur when an event was sent to the destination and encountered timeout error, and retries for the events are attempted. While the retries are attempted, and a Destination Filter is then added, these retries will not subject to the filtering since these are from the events sent before the Destination Filter is added."
pwseg
added
the
content-update
pwseg
approved these changes
Aug 25, 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 are confused that sometimes they are still seeing events flowing through after adding Destination Filter. Added the following faq to indicate that retries could account for these events not filtered by Destination Filter
"Why do I see events being sent through after I just added a destination filter?
If Event Delivery page shows events have been retried, the retries could account for events that did not get filtered when the Destination Filter is just added. Such scenario can occur when an event was sent to the destination and encountered timeout error, and retries for the events are attempted. While the retries are attempted, and a Destination Filter is then added, these retries will not subject to the filtering since these are from the events sent before the Destination Filter is added."
Merge timing
Related issues (optional)
https://segment.zendesk.com/agent/tickets/518110
https://segment.zendesk.com/agent/tickets/380271