Skip to content

Commit 5796bc1

Browse files
md5 hashing info
1 parent 56850a7 commit 5796bc1

File tree

1 file changed

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

1 file changed

+7
-0
lines changed

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,10 @@ You can do this for as many sources as you need.
2525
![A screenshot of the Write Keys field in the Repeater destination settings page.](images/write-key-settings.png)
2626

2727
Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.
28+
29+
## Repeater FAQ
30+
31+
##### What is the `context.repeatChain` field that I can see on my repeated events?
32+
33+
The `context.repeatChain` array that you will see on repeated events holds two values. The first will be the md5 hashed write key where the event originated. The second will be the md5 hashed write key that the event was sent to through the Repeater. This behavior exists to allow Segment to check to make sure the event isn't being sent to a pipeline that will result in an infinite loop.
34+

0 commit comments

Comments
 (0)