: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.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
fix(billing): preserve sources sync warnings and rename billing copy (#116770)
Pawel Cebula141eff5acbef
diff --git a/ee/hogai/tools/read_billing_tool/prompts.py b/ee/hogai/tools/read_billing_tool/prompts.pyindex 865c7590b380..672b5ca43c44 100644--- a/ee/hogai/tools/read_billing_tool/prompts.py+++ b/ee/hogai/tools/read_billing_tool/prompts.py@@ -192,7 +192,7 @@ See: https://posthog.com/docs/feature-flags/cutting-costs5. **Issue suppression**: Mark recurring unwanted issues as "Suppressed" to prevent future exceptions of the same type from being ingestedSee: https://posthog.com/docs/error-tracking/cutting-costs-#### Data Warehouse Cost Reduction+#### Sources cost reduction1. **Use incremental syncing**: Choose incremental over full table replication, which should only be used when you need to sync data deletions or tables lack incrementing fields, see: https://posthog.com/docs/cdp/sources#incremental-vs-full-table2. **Select proper replication keys**: Use appropriate fields like `updated_at` timestamps or autoincrementing IDs as replication keys for incremental syncing3. **Control sync frequency**: Adjust how often tables sync in the sources page to reduce unnecessary data transfers, see: https://posthog.com/docs/cdp/sources#syncingdiff --git a/frontend/src/queries/nodes/DataNode/warehouseSyncWarnings.test.ts b/frontend/src/queries/nodes/DataNode/warehouseSyncWarnings.test.tsindex cb179d83de26..9c290c01bb11 100644--- a/frontend/src/queries/nodes/DataNode/warehouseSyncWarnings.test.ts+++ b/frontend/src/queries/nodes/DataNode/warehouseSyncWarnings.test.ts@@ -35,8 +35,8 @@ describe('warehouseSyncWarnings', () => {],['billing limit reached drops the redundant tail',- 'Sync of `t` (from Stripe) is paused because the data warehouse billing limit has been reached. Results may be out of date.',- 'Sync of `t` (from Stripe) is paused because the data warehouse billing limit has been reached.',+ 'Sync of `t` (from Stripe) is paused because the Sources billing limit has been reached. Results may be out of date.',+ 'Sync of `t` (from Stripe) is paused because the Sources billing limit has been reached.',],['billing limit too low drops the redundant tail',diff --git a/frontend/src/scenes/billing/billing-utils.spec.ts b/frontend/src/scenes/billing/billing-utils.spec.tsindex da27f1db57a0..6976c01a9541 100644--- a/frontend/src/scenes/billing/billing-utils.spec.ts+++ b/frontend/src/scenes/billing/billing-utils.spec.ts@@ -476,8 +476,8 @@ describe('formatProductNames', () => {})describe('getUsageLimitConsequence', () => {- it('should return specific message for Data warehouse', () => {- expect(getUsageLimitConsequence('Data warehouse')).toEqual('data will not be synced')+ it.each(['Data warehouse', 'Sources'])('should return the sync consequence for %s', (name) => {+ expect(getUsageLimitConsequence(name)).toEqual('data will not be synced')})it('should return specific message for Feature flags & Experiments', () => {@@ -517,6 +517,13 @@ describe('buildUsageLimitReachedMessage', () => {expect(result.message).toContain('upgrade your plan')})+ it.each(['Data warehouse', 'Sources'])('should explain stopped syncing for %s at its usage limit', (name) => {+ const result = buildUsageLimitReachedMessage([{ type: 'data_warehouse', name, subscribed: true }])+ expect(result.message).toEqual(+ `You have reached the usage limit for ${name}. Please increase your billing limit or data will not be synced.`+ )+ })+it('should build message for multiple products with unique consequences', () => {const result = buildUsageLimitReachedMessage([{ name: 'Session replay', subscribed: true },diff --git a/frontend/src/scenes/billing/billing-utils.ts b/frontend/src/scenes/billing/billing-utils.tsindex f840f8655016..4a4fe0890dfb 100644--- a/frontend/src/scenes/billing/billing-utils.ts+++ b/frontend/src/scenes/billing/billing-utils.ts@@ -702,7 +702,7 @@ export function formatProductNames(names: string[]): string {* Get the consequence message for a product when it reaches its usage limit*/export function getUsageLimitConsequence(productName: string): string {- if (productName === 'Data warehouse') {+ if (productName === 'Data warehouse' || productName === 'Sources') {return 'data will not be synced'}if (productName === 'Feature flags & Experiments') {diff --git a/frontend/src/scenes/hog-functions/sub-templates/sub-templates.ts b/frontend/src/scenes/hog-functions/sub-templates/sub-templates.tsindex e515f0418ef9..6f757fc79245 100644--- a/frontend/src/scenes/hog-functions/sub-templates/sub-templates.ts+++ b/frontend/src/scenes/hog-functions/sub-templates/sub-templates.ts@@ -809,7 +809,7 @@ export const HOG_FUNCTION_SUB_TEMPLATES: Record<HogFunctionSubTemplateIdType, Ho'data-warehouse-billing-limit-reached': notificationVariants({subTemplateId: 'data-warehouse-billing-limit-reached',nameSuffix: 'when the billing limit stops a sync',- description: 'Know when the data warehouse billing limit stops a table from syncing',+ description: 'Know when the Sources billing limit stops a table from syncing',webhookDescription: 'Send billing limit events to your own endpoint',slackMessage: dwhBillingLimitMessage(DWH_SLACK_FIELDS, '*'),slackFallbackText: 'The billing limit stopped a table sync',diff --git a/products/billing/skills/understanding-billing-usage/SKILL.md b/products/billing/skills/understanding-billing-usage/SKILL.mdindex 9786813bb191..e534b6284dd4 100644--- a/products/billing/skills/understanding-billing-usage/SKILL.md+++ b/products/billing/skills/understanding-billing-usage/SKILL.md@@ -172,7 +172,7 @@ project/team or switch to it when the client exposes a project switcher. Use`references/usage-type-routing.md` to choose the product MCP surface.The deeper investigation must use data the customer can access in their own project:-events, feature flags, Error Tracking, Surveys, Session Replay, Data Warehouse sources,+events, feature flags, Error Tracking, Surveys, Session Replay, Sources,CDP functions, Logs, AI Observability, Workflows, Replay Vision, Signals/Inbox, orother product tools. Do not ask the customer-facing agent to query internal Billingtables, internal PostHog org data, or PostHog-owned telemetry for their organization.diff --git a/products/billing/skills/understanding-billing-usage/references/usage-type-routing.md b/products/billing/skills/understanding-billing-usage/references/usage-type-routing.mdindex c30b0d3f4101..33ebad001450 100644--- a/products/billing/skills/understanding-billing-usage/references/usage-type-routing.md+++ b/products/billing/skills/understanding-billing-usage/references/usage-type-routing.md@@ -19,7 +19,7 @@ Useful downstream skills for usage investigations include:- `posthog:investigating-error-issue` after Error Tracking has identified a dominant issue.- `posthog:investigating-replay` when Session Replay drilldown has representative recordings.- `posthog:auditing-warehouse-source-health` and `posthog:diagnosing-failed-warehouse-syncs`- for Data Warehouse source or sync issues.+ for Sources health or sync issues.- `posthog:investigating-logs` for Logs ingestion spikes or drops.- `posthog:exploring-llm-costs` and `posthog:analyzing-expensive-users` for AIObservability spend or credit drivers.@@ -28,32 +28,32 @@ Useful downstream skills for usage investigations include:- `posthog:exploring-replay-vision-observations` when Replay Vision credits point to scannerobservations.-| Usage type | What Billing can show | Customer-visible follow-up |-| ------------------------------------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| `event_count_in_period` | Events by day/project | Use `posthog:investigate-metric` or Product Analytics SQL/insight tools on the affected project. Break down by event name and compare the alert/high-usage day to baseline days. If `$autocapture` dominates, continue with `posthog:exploring-autocapture-events`. |-| `enhanced_persons_event_count_in_period` | Identified events by day/project | Start like Events, using `posthog:investigate-metric` when available, but avoid claiming the raw event-name breakdown exactly explains the identified/anonymous split unless that dimension is visible. |-| `group_analytics` | Group Analytics spend/usage attribution using identified-event usage | Treat as an alias-style product view. Use identified-event/Product Analytics drilldown, usually via `posthog:investigate-metric`, and explain that the Billing view is product-specific attribution, not a separate raw event stream. |-| `recording_count_in_period` | Session recordings by day/project | Use Session Replay tools or the Replay UI for recording volume, SDK/platform filters, and representative sessions. Use `posthog:investigating-replay` only after you have representative recording/session IDs. |-| `mobile_recording_count_in_period` | Mobile recordings by day/project | Use Session Replay/mobile replay surfaces. Look for mobile SDK/platform mix before suggesting product changes. Use `posthog:investigating-replay` only after you have representative mobile recording/session IDs. |-| `billable_feature_flag_requests_count_in_period` | Feature flag requests by day/project | Use feature flag tools, flag configuration, and activity history. The billable unit is flag evaluation/API request volume, not `$feature_flag_called` events. Do not use stale-flag cleanup workflows unless the user asks how to remove unused flags. |-| `exceptions_captured_in_period` | Exceptions by day/project | Use Error Tracking issue tools and `$exception` aggregates in the affected project. If one issue dominates the movement, use `posthog:investigating-error-issue`. UI issue counts are grouped context, while Billing usage is captured exception volume. |-| `survey_responses_count_in_period` | Survey responses by day/project | Use survey tools and survey events such as `survey shown` and `survey sent` to distinguish reach from response-rate changes. Use `posthog:debugging-surveys` when the investigation turns into "why is this survey showing, not showing, or getting fewer/more responses than expected?" |-| `ai_event_count_in_period` | AI Observability events by day/project | Use AI Observability tools or SQL over `$ai_*` events in the affected project. Break down by provider/model/trace/user only when those properties are available. Use `posthog:exploring-llm-costs` for cost-shaped questions and `posthog:analyzing-expensive-users` for user-level drivers. |-| `ai_credits_used_in_period` | PostHog AI credits by day/project | Use PostHog AI or AI Observability surfaces exposed to the user. Prefer `posthog:exploring-llm-costs` for credit/spend movement and `posthog:analyzing-expensive-users` for concentrated user drivers. Do not inspect internal PostHog-owned AI telemetry in a customer-facing investigation. |-| `signals_credits_used_in_period` | Inbox credits by day/project | Use Signals/Inbox product tools when available. Start with `posthog:inbox-exploration` for report-level context; use `posthog:signals` only when raw signal search is needed. Billing shows chargeable credit movement; product tools should explain reports/PRs/refunds. |-| `posthog_code_credits_used_in_period` | PostHog Desktop credits by day/project | Use PostHog Desktop usage surfaces when available. Treat token credits and sandbox compute as possible sub-drivers if exposed. |-| `posthog_code_token_credits_used_in_period` | PostHog Desktop token credits by day/project | Use PostHog Desktop/AI usage surfaces when available. |-| `sandbox_compute_credits_used_in_period` | Sandbox compute credits by day/project | Use task/sandbox/PostHog Desktop surfaces when available. |-| `sandbox_compute_cpu_millicore_seconds_in_period` | Sandbox CPU usage by day/project | Use task/sandbox surfaces when available. This is a raw usage diagnostic, not usually the headline spend type. |-| `sandbox_compute_memory_mib_seconds_in_period` | Sandbox memory usage by day/project | Use task/sandbox surfaces when available. This is a raw usage diagnostic, not usually the headline spend type. |-| `rows_synced_in_period` | Data Warehouse synced rows by day/project | Use Data Warehouse source/schema health and sync tools. Look for new sources, enabled schemas, failed/stale syncs, or expected backfills. Use `posthog:auditing-warehouse-source-health` for a project-wide scan and `posthog:diagnosing-failed-warehouse-syncs` for a specific source/schema. |-| `free_historical_rows_synced_in_period` | Historical synced rows by day/project | Use Data Warehouse source/schema tools. Explain it as historical sync activity, not ongoing incremental volume. Use `posthog:auditing-warehouse-source-health` or `posthog:diagnosing-failed-warehouse-syncs` if a source or schema needs investigation. |-| `rows_exported_in_period` | Batch export rows by day/project | Use batch export/CDP export tools and export configuration. Check newly enabled exports or changed destinations. |-| `data_pipelines` | Legacy Data Pipelines product attribution | Treat as a legacy/synthetic product view. Use the Product Analytics or CDP surface that actually produced the usage, depending on the user's context. |-| `cdp_billable_invocations_in_period` | Realtime destination trigger events by day/project | Use CDP function tools: list functions, inspect enabled destinations, metrics, and logs for the affected window. |-| `workflow_emails_sent_in_period` | Workflow emails by day/project | Use Workflows tools: workflow stats, invocation logs, enabled workflows, and recent changes. |-| `workflow_billable_invocations_in_period` | Workflow destination dispatches by day/project | Use Workflows tools and destination/invocation logs. Keep it separate from email volume. |-| `logs_mb_in_period` | Logs ingested in MB by day/project | Use `posthog:investigating-logs` with Logs tools: service overview, count ranges, facets, and pattern diffs. Prefer log-specific tools over raw SQL. |-| `logs_retention_30d_mb_in_period` | Logs ingested under 30-day retention by day/project | Use `posthog:investigating-logs` with Logs tools and retention/settings surfaces. Explain that this is retention-tier usage, not separate log content. |-| `logs_retention_mb_days_in_period` | Logs retention in MB-days (bytes ingested weighted by retention days) by day/project | Use `posthog:investigating-logs` with Logs tools and retention/settings surfaces. Explain that this is storage-duration usage (MB times days retained), not separate log content. Average retention days = this / `logs_mb_in_period`. |-| `replay_vision_credits_used_in_period` | Replay Vision credits by day/project | Use Replay Vision scanner/observation tools. Credits come from scanner observations, so inspect scanners and observation status/results. Use `posthog:exploring-replay-vision-observations` when scanner observations are the natural drilldown. |+| Usage type | What Billing can show | Customer-visible follow-up |+| ------------------------------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| `event_count_in_period` | Events by day/project | Use `posthog:investigate-metric` or Product Analytics SQL/insight tools on the affected project. Break down by event name and compare the alert/high-usage day to baseline days. If `$autocapture` dominates, continue with `posthog:exploring-autocapture-events`. |+| `enhanced_persons_event_count_in_period` | Identified events by day/project | Start like Events, using `posthog:investigate-metric` when available, but avoid claiming the raw event-name breakdown exactly explains the identified/anonymous split unless that dimension is visible. |+| `group_analytics` | Group Analytics spend/usage attribution using identified-event usage | Treat as an alias-style product view. Use identified-event/Product Analytics drilldown, usually via `posthog:investigate-metric`, and explain that the Billing view is product-specific attribution, not a separate raw event stream. |+| `recording_count_in_period` | Session recordings by day/project | Use Session Replay tools or the Replay UI for recording volume, SDK/platform filters, and representative sessions. Use `posthog:investigating-replay` only after you have representative recording/session IDs. |+| `mobile_recording_count_in_period` | Mobile recordings by day/project | Use Session Replay/mobile replay surfaces. Look for mobile SDK/platform mix before suggesting product changes. Use `posthog:investigating-replay` only after you have representative mobile recording/session IDs. |+| `billable_feature_flag_requests_count_in_period` | Feature flag requests by day/project | Use feature flag tools, flag configuration, and activity history. The billable unit is flag evaluation/API request volume, not `$feature_flag_called` events. Do not use stale-flag cleanup workflows unless the user asks how to remove unused flags. |+| `exceptions_captured_in_period` | Exceptions by day/project | Use Error Tracking issue tools and `$exception` aggregates in the affected project. If one issue dominates the movement, use `posthog:investigating-error-issue`. UI issue counts are grouped context, while Billing usage is captured exception volume. |+| `survey_responses_count_in_period` | Survey responses by day/project | Use survey tools and survey events such as `survey shown` and `survey sent` to distinguish reach from response-rate changes. Use `posthog:debugging-surveys` when the investigation turns into "why is this survey showing, not showing, or getting fewer/more responses than expected?" |+| `ai_event_count_in_period` | AI Observability events by day/project | Use AI Observability tools or SQL over `$ai_*` events in the affected project. Break down by provider/model/trace/user only when those properties are available. Use `posthog:exploring-llm-costs` for cost-shaped questions and `posthog:analyzing-expensive-users` for user-level drivers. |+| `ai_credits_used_in_period` | PostHog AI credits by day/project | Use PostHog AI or AI Observability surfaces exposed to the user. Prefer `posthog:exploring-llm-costs` for credit/spend movement and `posthog:analyzing-expensive-users` for concentrated user drivers. Do not inspect internal PostHog-owned AI telemetry in a customer-facing investigation. |+| `signals_credits_used_in_period` | Inbox credits by day/project | Use Signals/Inbox product tools when available. Start with `posthog:inbox-exploration` for report-level context; use `posthog:signals` only when raw signal search is needed. Billing shows chargeable credit movement; product tools should explain reports/PRs/refunds. |+| `posthog_code_credits_used_in_period` | PostHog Desktop credits by day/project | Use PostHog Desktop usage surfaces when available. Treat token credits and sandbox compute as possible sub-drivers if exposed. |+| `posthog_code_token_credits_used_in_period` | PostHog Desktop token credits by day/project | Use PostHog Desktop/AI usage surfaces when available. |+| `sandbox_compute_credits_used_in_period` | Sandbox compute credits by day/project | Use task/sandbox/PostHog Desktop surfaces when available. |+| `sandbox_compute_cpu_millicore_seconds_in_period` | Sandbox CPU usage by day/project | Use task/sandbox surfaces when available. This is a raw usage diagnostic, not usually the headline spend type. |+| `sandbox_compute_memory_mib_seconds_in_period` | Sandbox memory usage by day/project | Use task/sandbox surfaces when available. This is a raw usage diagnostic, not usually the headline spend type. |+| `rows_synced_in_period` | Sources synced rows by day/project | Use Sources health and sync tools. Look for new sources, enabled schemas, failed/stale syncs, or expected backfills. Use `posthog:auditing-warehouse-source-health` for a project-wide scan and `posthog:diagnosing-failed-warehouse-syncs` for a specific source/schema. |+| `free_historical_rows_synced_in_period` | Historical synced rows by day/project | Use Sources tools. Explain it as historical sync activity, not ongoing incremental volume. Use `posthog:auditing-warehouse-source-health` or `posthog:diagnosing-failed-warehouse-syncs` if a source or schema needs investigation. |+| `rows_exported_in_period` | Batch export rows by day/project | Use batch export/CDP export tools and export configuration. Check newly enabled exports or changed destinations. |+| `data_pipelines` | Legacy Data Pipelines product attribution | Treat as a legacy/synthetic product view. Use the Product Analytics or CDP surface that actually produced the usage, depending on the user's context. |+| `cdp_billable_invocations_in_period` | Realtime destination trigger events by day/project | Use CDP function tools: list functions, inspect enabled destinations, metrics, and logs for the affected window. |+| `workflow_emails_sent_in_period` | Workflow emails by day/project | Use Workflows tools: workflow stats, invocation logs, enabled workflows, and recent changes. |+| `workflow_billable_invocations_in_period` | Workflow destination dispatches by day/project | Use Workflows tools and destination/invocation logs. Keep it separate from email volume. |+| `logs_mb_in_period` | Logs ingested in MB by day/project | Use `posthog:investigating-logs` with Logs tools: service overview, count ranges, facets, and pattern diffs. Prefer log-specific tools over raw SQL. |+| `logs_retention_30d_mb_in_period` | Logs ingested under 30-day retention by day/project | Use `posthog:investigating-logs` with Logs tools and retention/settings surfaces. Explain that this is retention-tier usage, not separate log content. |+| `logs_retention_mb_days_in_period` | Logs retention in MB-days (bytes ingested weighted by retention days) by day/project | Use `posthog:investigating-logs` with Logs tools and retention/settings surfaces. Explain that this is storage-duration usage (MB times days retained), not separate log content. Average retention days = this / `logs_mb_in_period`. |+| `replay_vision_credits_used_in_period` | Replay Vision credits by day/project | Use Replay Vision scanner/observation tools. Credits come from scanner observations, so inspect scanners and observation status/results. Use `posthog:exploring-replay-vision-observations` when scanner observations are the natural drilldown. |diff --git a/products/data_warehouse/backend/sync_status.py b/products/data_warehouse/backend/sync_status.pyindex b37f58dd152d..dbfb06cfb7d4 100644--- a/products/data_warehouse/backend/sync_status.py+++ b/products/data_warehouse/backend/sync_status.py@@ -27,7 +27,7 @@ STALE_RUNNING_MULTIPLIER = 2_NOT_DELETED = Q(deleted=False) | Q(deleted__isnull=True)_BILLING_LIMIT_REASONS: dict[str, str] = {- ExternalDataSchemaStatus.BILLING_LIMIT_REACHED: "the data warehouse billing limit has been reached",+ ExternalDataSchemaStatus.BILLING_LIMIT_REACHED: "the Sources billing limit has been reached",ExternalDataSchemaStatus.BILLING_LIMIT_TOO_LOW: "the configured billing limit is too low",}diff --git a/products/data_warehouse/frontend/shared/components/FreeHistoricalSyncsBanner.tsx b/products/data_warehouse/frontend/shared/components/FreeHistoricalSyncsBanner.tsxindex a0ba3f90a3a9..0b49e1c0f2d7 100644--- a/products/data_warehouse/frontend/shared/components/FreeHistoricalSyncsBanner.tsx+++ b/products/data_warehouse/frontend/shared/components/FreeHistoricalSyncsBanner.tsx@@ -95,7 +95,7 @@ export function FreeHistoricalSyncsBanner({ hideGetStarted }: { hideGetStarted?:)}<p className="text-sm opacity-70">- After the first 7-day period, standard data warehouse pricing will apply.+ After the first 7-day period, standard Sources pricing will apply.</p></div></LemonModal>diff --git a/products/warehouse_sources/backend/temporal/data_imports/cdc/billing_expiry.py b/products/warehouse_sources/backend/temporal/data_imports/cdc/billing_expiry.pyindex 6cc8d19d8a2c..e38223759e1f 100644--- a/products/warehouse_sources/backend/temporal/data_imports/cdc/billing_expiry.py+++ b/products/warehouse_sources/backend/temporal/data_imports/cdc/billing_expiry.py@@ -32,12 +32,12 @@ if typing.TYPE_CHECKING:BILLING_LIMIT_EXPIRED_REASON = "billing_limit_expired"_SLOT_DROPPED_MESSAGE = (- "Change data capture stopped because this team has been over its data warehouse billing limit for "+ "Change data capture stopped because this team has been over its Sources billing limit for ""14 days, and PostHog keeps captured changes for 14 days. PostHog dropped the replication slot. ""Once you're back under the limit, use Repair CDC to recreate it and re-sync your tables.")_SLOT_KEPT_MESSAGE = (- "Change data capture stopped loading because this team has been over its data warehouse billing "+ "Change data capture stopped loading because this team has been over its Sources billing ""limit for 14 days, and PostHog keeps captured changes for 14 days. The replication slot was not ""dropped. Once you're back under the limit, your tables re-sync on their own.")diff --git a/products/warehouse_sources/backend/temporal/data_imports/pipelines/common/extract.py b/products/warehouse_sources/backend/temporal/data_imports/pipelines/common/extract.pyindex 9247688e4fc9..4e394e5f88c1 100644--- a/products/warehouse_sources/backend/temporal/data_imports/pipelines/common/extract.py+++ b/products/warehouse_sources/backend/temporal/data_imports/pipelines/common/extract.py@@ -502,7 +502,7 @@ async def setup_row_tracking_with_billing_check(await increment_rows(team_id, schema.id, resource.rows_to_sync)if await will_hit_billing_limit(team_id=team_id, source=source, logger=logger):raise BillingLimitsWillBeReachedException(- f"Your account will hit your Data Warehouse billing limits syncing {resource.name} "+ f"Your account will hit your Sources billing limits syncing {resource.name} "f"with {resource.rows_to_sync} rows")diff --git a/products/warehouse_sources/backend/temporal/data_imports/pipelines/core/arrow_utils.py b/products/warehouse_sources/backend/temporal/data_imports/pipelines/core/arrow_utils.pyindex 7d07c877fe0b..52669084b96f 100644--- a/products/warehouse_sources/backend/temporal/data_imports/pipelines/core/arrow_utils.py+++ b/products/warehouse_sources/backend/temporal/data_imports/pipelines/core/arrow_utils.py@@ -59,7 +59,7 @@ type DecimalInput = decimal.Decimal | float | str | tuple[int, Sequence[int], inclass BillingLimitsWillBeReachedException(NonReportableError):- """The sync was intentionally halted because the account will cross its Data Warehouse billing+ """The sync was intentionally halted because the account will cross its Sources billinglimit. Expected control flow, not a defect: the workflow marks the job BILLING_LIMIT_TOO_LOW,and subclassing NonReportableError keeps it out of error tracking."""