From 6bcc84fbfd662f72ce3b38429ce9205a9063f783 Mon Sep 17 00:00:00 2001
From: Vaishnavi Pandey <83347579+Vaishnavi-Pandey12@users.noreply.github.com>
Date: Mon, 15 Dec 2025 10:19:58 +0530
Subject: [PATCH] [BEAM-9917] Document BigQuery file load behavior with dynamic
 destinations

---
 .../content/en/documentation/io/built-in/google-bigquery.md  | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/website/www/site/content/en/documentation/io/built-in/google-bigquery.md b/website/www/site/content/en/documentation/io/built-in/google-bigquery.md
index 9c205f092663..ba6ccf2ceb8a 100644
--- a/website/www/site/content/en/documentation/io/built-in/google-bigquery.md
+++ b/website/www/site/content/en/documentation/io/built-in/google-bigquery.md
@@ -659,6 +659,11 @@ runtime. The sharding behavior depends on the runners.
 You must use `triggering_frequency` to specify a triggering frequency for
 initiating load jobs. Be careful about setting the frequency such that your
 pipeline doesn't exceed the BigQuery load job [quota limit](https://cloud.google.com/bigquery/quotas#load_jobs).
+
+> **Note:** When using file load-based BigQuery writes with dynamic destinations and a non-zero
+> `triggering_frequency`, temporary tables may be created repeatedly and loads
+> are not finalized into destination tables. This is a known limitation (see BEAM-9917).
+
 {{< /paragraph >}}
 
 {{< paragraph class="language-py" >}}