You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/repeater/index.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,3 +25,10 @@ You can do this for as many sources as you need.
25
25

26
26
27
27
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.
0 commit comments