From 8446aff70f2b89123682e481f34b790550182c03 Mon Sep 17 00:00:00 2001
From: runllm <support@runllm.com>
Date: Fri, 18 Apr 2025 12:02:29 +0000
Subject: [PATCH] Update docs-propagation.md

---
 docs/automations/docs-propagation.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/docs/automations/docs-propagation.md b/docs/automations/docs-propagation.md
index e8eba08d3640e..44027b4d123b5 100644
--- a/docs/automations/docs-propagation.md
+++ b/docs/automations/docs-propagation.md
@@ -125,4 +125,15 @@ used to propagate the description.
 
 <p align="left">
   <img width="50%"  src="https://raw.githubusercontent.com/datahub-project/static-assets/main/imgs/automation/oss/docs-propagation/view-propagated-docs.png"/>
-</p>
\ No newline at end of file
+</p>
+
+## Troubleshooting Documentation Propagation Issues
+
+If you encounter issues with documentation propagation, consider the following steps:
+
+1. **Verify Propagation Settings**: Ensure that the feature is enabled as described above.
+2. **Check Lineage Configuration**: Use the DataHub UI to verify column-level lineage connections.
+3. **Review Ingestion Logs**: Check logs for any errors or warnings related to metadata propagation.
+4. **Manual Verification**: Inspect the DataHub UI or use the DataHub Python SDK to verify column descriptions.
+
+For more advanced scenarios, consider reviewing the source code or using the action framework for custom propagation logic.
\ No newline at end of file