Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitb6298de

Browse files
authored
Merge pull requestsegmentio#5223 from segmentio/tanjinhong72-patch-2
Add faq that retries could account for events not filtered by Destination Filter
2 parents6545f90 +fb7521e commitb6298de

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

‎src/connections/destinations/destination-filters.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -229,3 +229,9 @@ Destination Filters can't target properties or traits with spaces in the field n
229229
####Can I use destination filters to drop events unsupported by a destination?
230230

231231
The check for unsupported events types happens before any destination filter checks. As a result, Destination Filters can't prevent unsupported event type errors. To filter these events, use the[Integrations Object](/docs/guides/filtering-data/#filtering-with-the-integrations-object).
232+
233+
####Why do I see events sent through after I just added a destination filter?
234+
235+
Destination filters only filter events sent after filter setup. If you just added a destination filter but still see some events going through, you're likely seeing retries from failed events that occurred before you set up the filter.
236+
237+
When Segment sends an event to a destination but encounters a timeout error, it attempts to send the event again. As a result, if you add a destination filter while Segment is trying to send a failed event, these retries could filter through, since they reflect events that occurred before filter setup.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp