diff --git a/docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md b/docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md
index cc4a825af..908b5b382 100644
--- a/docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md
+++ b/docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md
@@ -4,7 +4,7 @@ ___
| 15 minutes read |
Level: Intermediate |
- Last Updated: October 2025 |
+ Last Updated: December 2025 |
@@ -68,6 +68,14 @@ ___
- Dynamic Menu: Read items from a sheet and send them as interactive list options.
+### Google Sheet Sync
+
+- When content to a linked google sheet in read mode is updated, the sheet needs to be `synced` using the sync button corresponding to the google sheet.
+- This ensures that the latest modifications made in the google sheet are available to use in the Glific flows where the sheet is being used.
+- Google sheet in read-mode and on auto-sync functionality sync every 24 hours. The google sync operations happen between 5-6am IST
+- To handle use case which demand that the google sheets be synced more than once a day or as per a custom logic, read more [here](https://docs.google.com/document/d/1Hix2ShKMJqfhOHrTc4GAT2JWc3ThyuZ8RvdO61wc2d4/edit?usp=sharing)
+- If the google sheet fails to sync, the flow continues to send older content.
+- To troubleshoot sheet sync failure errors, read more in FAQ section.
### Why to use Write Mode of Google Sheet
diff --git a/docs/8. FAQ/Why is the google sheet sync failing.md b/docs/8. FAQ/Why is the google sheet sync failing.md
new file mode 100644
index 000000000..5fd995132
--- /dev/null
+++ b/docs/8. FAQ/Why is the google sheet sync failing.md
@@ -0,0 +1,35 @@
+# Why is the Google Sheet sync failing?
+
+Google sheets on read mode with auto-sync functionality turned on sync once in every 24 hours. The sync operations happens around 5-6 am IST. If google sheet fails to sync, there is an error condition that is displayed on the google sheets page.
+
+This document details out the error conditions that make the google sheets sync to fail, and how to solve these situations are explained below.
+
+## 1. Key can’t be blank
+This happens when the `Key` columns is either empty or contains a few blank cells like shown. To solve this make sure that there are no empty cells in `Key`
+
+
+
+## 2. Unknown error or empty content
+
+This happens when the sheet is empty or if the sheet does not contain a `Key` column. If the sheet is not empty and this error condition persists, it is likely because the Google Sheet contains a large amount of data. In such cases, the Google Sheet should be added as a table to the organization's BigQuery, and a serverless webhook should be deployed in Google Cloud Run to query the information when called from Glific. Refer to [this BigQuery and Cloud Run integration guide](https://docs.google.com/document/d/1C5FHnZuK38ukcR88ToVR689CHm6m6ijQ3zMxg6J5MRI/edit?tab=t.0#heading=h.e7zpjexh7kel) for implementation details.
+
+## 3. Key: has already been taken
+
+This happens when the Values in “Key” column is repeated more than once. To solve this ensure that, `Key` column contains only unique values.
+
+## 4. Sheet not found or inaccessible
+
+This happens if the sheet permissions are not in order. To use “read from google sheet” capability, the google sheet being used should have “anyone with the link” can “view” permission.
+
+This condition could also occur in case the sheet is deleted from the google drive.
+
+## 5. Repeated or missing headers
+This condition happens when there are headers which are repeated, or if there are any columns where content is present but header is not specified (screenshot shows an example of sheet with missing header)
+
+
+
+
+To solve this, make sure that the headers have unique names. Also, ensure that all columns where content is present have a named header.
+
+
+