Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(ai-research): state the v4 flush_id format (#128272)

Robbie52d338b1e461
diff --git a/products/ai_training/docs/replay-data.md b/products/ai_training/docs/replay-data.md
index dac9aaa2f865..d3af6f456851 100644
--- a/products/ai_training/docs/replay-data.md
+++ b/products/ai_training/docs/replay-data.md
@@ -537,6 +537,7 @@ When the partition moves first, or the process restarts, the next attempt for th
A retry can also cover a different range than the attempt it replaces, for example one flush that replays two earlier flushes.
Every row therefore names its flush and its Kafka position.
The index rows are published without waiting for delivery, so a retry can also reach the index only in part.
+`flush_id` is a random 64-bit number for each attempt, written as 16 lowercase hexadecimal digits, so its text order is its numeric order.
Every row of one (`flush_id`, `topic`, `partition`) carries the same `flush_end_offset` and `flush_row_count`, and its own `flush_row_index` from 0.
Readers drop duplicates with one rule per (`topic`, `partition`), applied to all rows before any session or team filter: