Skip to content

Commit 581bb54

Browse files
authored
Merge pull request #4253 from segmentio/lizkane222-patch-6
Update replay considerations
2 parents 90518a1 + 36cce63 commit 581bb54

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/guides/what-is-replay.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,9 @@ For more information, [Contact us](https://segment.com/help/contact/) and our Su
2828

2929
Replays are currently only available for Business Tier customers, and due to their complex nature are not self-serve. [Contact us](https://segment.com/help/contact/) to learn more, or to request a replay for your workspace. When requesting a replay, include the workspace, the source to replay from, the destination tool or tools, and the time period.
3030

31-
Replays can process an unlimited amount of data, however they are rate limited to respect the limitations in downstream partner tools. The replay time depends on the tool we're replaying to, and the amount of data included in the replay.
31+
Replays can process unlimited data, but they're rate limited to respect limitations in downstream partner tools. If you're also sending data to the destination being replayed to in real time, then, when determining your replay's limit, you'll want to take into account the rate limit being used by real-time events. You should also account for a small margin of your rate limit to allow events to be retried.
32+
33+
Replay time depends both on the tool Segment replays to and the amount of data included in the replay.
3234

3335
Replays do not affect your [MTU count](/docs/guides/usage-and-billing/mtus-and-throughput/), unless you are using a [Repeater destination](/docs/connections/destinations/catalog/repeater/). Notify your team before initiating a Replay if you're using a Repeater destination.
3436

0 commit comments

Comments
 (0)