diff --git a/openmetadata-docs/content/v1.6.x/deployment/ingestion/external/airflow.md b/openmetadata-docs/content/v1.6.x/deployment/ingestion/external/airflow.md
index 87e51a57b97..017e1737e3d 100644
--- a/openmetadata-docs/content/v1.6.x/deployment/ingestion/external/airflow.md
+++ b/openmetadata-docs/content/v1.6.x/deployment/ingestion/external/airflow.md
@@ -141,7 +141,19 @@ with models.DAG(
 
 {% note %}
 
-Make sure to tune out the DAG configurations (`schedule_interval`, `start_date`, etc.) as your use case requires.
+- Make sure to tune out the DAG configurations (`schedule_interval`, `start_date`, etc.) as your use case requires.
+
+{% /note %}
+
+{% note %}
+
+If you encounter issues such as missing task instances or Airflow failing to locate a deployed DAG (e.g., `Dag '<DAG_ID>' could not be found`), this may be due to a **timezone mismatch** in your Airflow configuration. To resolve this, set the following in your `airflow.cfg`:
+
+```ini
+default_timezone = system
+```
+
+This ensures that Airflow uses the system timezone, which is particularly important when OpenMetadata and Airflow are running on the same server.
 
 {% /note %}
 
diff --git a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/airflow.md b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/airflow.md
index a4bd1e94469..f283d169b46 100644
--- a/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/airflow.md
+++ b/openmetadata-docs/content/v1.7.x/deployment/ingestion/external/airflow.md
@@ -145,6 +145,18 @@ Make sure to tune out the DAG configurations (`schedule_interval`, `start_date`,
 
 {% /note %}
 
+{% note %}
+
+If you encounter issues such as missing task instances or Airflow failing to locate a deployed DAG (e.g., `Dag '<DAG_ID>' could not be found`), this may be due to a **timezone mismatch** in your Airflow configuration. To resolve this, set the following in your `airflow.cfg`:
+
+```ini
+default_timezone = system
+```
+
+This ensures that Airflow uses the system timezone, which is particularly important when OpenMetadata and Airflow are running on the same server.
+
+{% /note %}
+
 ### Key Notes
 
 - **Image Version**: Ensure the Docker image version matches your OpenMetadata server version (e.g., `openmetadata/ingestion-base:0.13.2`).  
diff --git a/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/ingestion/external/airflow.md b/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/ingestion/external/airflow.md
index dfbe3173938..74df8ad3c8b 100644
--- a/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/ingestion/external/airflow.md
+++ b/openmetadata-docs/content/v1.8.x-SNAPSHOT/deployment/ingestion/external/airflow.md
@@ -145,6 +145,18 @@ Make sure to tune out the DAG configurations (`schedule_interval`, `start_date`,
 
 {% /note %}
 
+{% note %}
+
+If you encounter issues such as missing task instances or Airflow failing to locate a deployed DAG (e.g., `Dag '<DAG_ID>' could not be found`), this may be due to a **timezone mismatch** in your Airflow configuration. To resolve this, set the following in your `airflow.cfg`:
+
+```ini
+default_timezone = system
+```
+
+This ensures that Airflow uses the system timezone, which is particularly important when OpenMetadata and Airflow are running on the same server.
+
+{% /note %}
+
 ### Key Notes
 
 - **Image Version**: Ensure the Docker image version matches your OpenMetadata server version (e.g., `openmetadata/ingestion-base:0.13.2`).