Skip to content

Commit b2b4e3b

Browse files
authored
Update FAQ language
1 parent 5796bc1 commit b2b4e3b

File tree

1 file changed

+1
-2
lines changed
  • src/connections/destinations/catalog/repeater

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,5 +30,4 @@ Repeater sends all events it receives to the sources you specified, identified b
3030

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

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-
33+
The `context.repeatChain` array that you will see on repeated events holds two values. The first value is the MD5-hashed write key where the event originated. The second value is the MD5-hashed write key that the event was sent to through the Repeater. This behavior lets Segment verify that the event isn't sent to a pipeline that will result in an infinite loop.

0 commit comments

Comments
 (0)