From c0cb3ab74532cb57ae464ae2ddea5e7e93503021 Mon Sep 17 00:00:00 2001 From: "inkeep[bot]" <257615677+inkeep[bot]@users.noreply.github.com> Date: Thu, 26 Feb 2026 10:34:11 +0000 Subject: [PATCH 1/2] docs: update batch exports backfill section with estimation phase, total records count, and early completion Reflects changes from PostHog/posthog#47788: - Document new STARTING status during estimation phase - Add total_records_count and adjusted_start_at fields - Document early completion when no matching data exists - Update phrasing since backfills no longer immediately schedule runs --- contents/docs/cdp/batch-exports/index.mdx | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/contents/docs/cdp/batch-exports/index.mdx b/contents/docs/cdp/batch-exports/index.mdx index 4aaea7df047c..5496e001e252 100644 --- a/contents/docs/cdp/batch-exports/index.mdx +++ b/contents/docs/cdp/batch-exports/index.mdx @@ -131,9 +131,15 @@ From here, you can create a new backfill by clicking the "Start backfill" button ![create historic export](https://res.cloudinary.com/dmukukwp6/image/upload/2024_08_09_at_14_54_54_90338968ac.png) -This will immediately schedule a series of batch export runs that fall within the bounds selected, based on the batch export's frequency. +After you start a backfill, PostHog first estimates the total number of records to export and validates the date range. During this estimation phase, the backfill shows a **Starting** status. Once estimation is complete, the status transitions to **Running** and the batch export runs begin. -The start date of a backfill may be adjusted depending on when the earliest available data is. For example, if you choose a start date of 2024-01-01 but the earliest event captured in PostHog is 2024-01-02, the start date will be adjusted to 2024-01-02. On the other hand, the end date of the backfill cannot be set past the current time, as our engineers have yet to figure out time traveling to allow us to export events in the future. +The start date of a backfill may be adjusted depending on when the earliest available data is. For example, if you choose a start date of 2024-01-01 but the earliest event captured in PostHog is 2024-01-02, the start date is adjusted to 2024-01-02. On the other hand, the end date of the backfill cannot be set past the current time. + +After estimation, a backfill tracks the following additional information: +- **Total records count** - An estimate of the total records to be exported. +- **Adjusted start date** - If your selected start date is earlier than your earliest available data, PostHog narrows it to avoid creating unnecessary batch runs. + +If the estimation finds no matching data to export, the backfill completes immediately with 0 records rather than creating empty batch runs. ## FAQ From a3adb2d4ae56d4d610ac6f1387404643bd313819 Mon Sep 17 00:00:00 2001 From: Ross Gray Date: Thu, 26 Feb 2026 15:30:44 +0000 Subject: [PATCH 2/2] Update copy --- contents/docs/cdp/batch-exports/index.mdx | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/contents/docs/cdp/batch-exports/index.mdx b/contents/docs/cdp/batch-exports/index.mdx index 5496e001e252..8b756b7edd66 100644 --- a/contents/docs/cdp/batch-exports/index.mdx +++ b/contents/docs/cdp/batch-exports/index.mdx @@ -131,15 +131,11 @@ From here, you can create a new backfill by clicking the "Start backfill" button ![create historic export](https://res.cloudinary.com/dmukukwp6/image/upload/2024_08_09_at_14_54_54_90338968ac.png) -After you start a backfill, PostHog first estimates the total number of records to export and validates the date range. During this estimation phase, the backfill shows a **Starting** status. Once estimation is complete, the status transitions to **Running** and the batch export runs begin. +After you start a backfill, PostHog first estimates the total number of records to export and validates the date range. -The start date of a backfill may be adjusted depending on when the earliest available data is. For example, if you choose a start date of 2024-01-01 but the earliest event captured in PostHog is 2024-01-02, the start date is adjusted to 2024-01-02. On the other hand, the end date of the backfill cannot be set past the current time. +The start date of a backfill may be adjusted depending on when the earliest available data is. For example, if you choose a start date of 2026-01-01 but the earliest event captured in PostHog is 2026-01-02, the start date is adjusted to 2026-01-02. On the other hand, the end date of the backfill cannot be set past the current time, as our engineers have yet to figure out time traveling to allow us to export events in the future. -After estimation, a backfill tracks the following additional information: -- **Total records count** - An estimate of the total records to be exported. -- **Adjusted start date** - If your selected start date is earlier than your earliest available data, PostHog narrows it to avoid creating unnecessary batch runs. - -If the estimation finds no matching data to export, the backfill completes immediately with 0 records rather than creating empty batch runs. +If the estimation finds no matching data to export, the backfill completes immediately rather than creating empty batch runs. ## FAQ