Skip to content

Commit 1202005

Browse files
Merge pull request #4801 from segmentio/lizkane222-patch-2
Update index.md repeater to include details on replay
2 parents c4f39b5 + 975630e commit 1202005

File tree

1 file changed

+8
-0
lines changed
  • src/connections/destinations/catalog/repeater

1 file changed

+8
-0
lines changed

src/connections/destinations/catalog/repeater/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,14 @@ You can do this for as many sources as you need.
2626

2727
Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.
2828

29+
## Replays with a Repeater destination
30+
31+
Running a Replay on a Repeater destination might count toward your MTUs, especially if you are replaying historical data from the source that flows data into your Repeater destination.
32+
33+
Because the API plans count by events sent through the pipeline and the Repeater destination resends an event through the entire pipeline, one event might flow through your source twice which increases the throughput count.
34+
35+
Segment recommends that you notify your team before initiating a Replay if you’re using a Repeater destination.
36+
2937
## Repeater FAQ
3038

3139
##### What is the `context.repeatChain` field that I can see on my repeated events?

0 commit comments

Comments
 (0)