diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md
index 122b60202..70f13d7c4 100644
--- a/src/UserGuide/Master/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/Master/User-Manual/Data-Sync_apache.md
@@ -92,7 +92,9 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
-![](https://alioss.timecho.com/docs/img/sync_en_02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
 
 Provide the following SQL statements for state management of synchronization tasks.
 
@@ -120,7 +122,7 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md
index 83a5aacbe..a54752c69 100644
--- a/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/Master/User-Manual/Data-Sync_timecho.md
@@ -94,7 +94,9 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
-![](https://alioss.timecho.com/docs/img/sync_en_02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
 
 Provide the following SQL statements for state management of synchronization tasks.
 
@@ -122,7 +124,7 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
index 7da2d03cb..8bfd5e39d 100644
--- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
@@ -92,8 +92,18 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
+V1.3.0 and earlier versions:
+
+After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task.
+
 ![](https://alioss.timecho.com/docs/img/sync_en_02.png)
 
+V1.3.1 and later versions:
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
+
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
 Provide the following SQL statements for state management of synchronization tasks.
 
 ### Create Task
@@ -120,7 +130,8 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
+
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
index 739f63092..81c1aeac3 100644
--- a/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
@@ -94,8 +94,19 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
+
+V1.3.0 and earlier versions:
+
+After creation, it will not start immediately and needs to execute the `START PIPE` statement to start the task.
+
 ![](https://alioss.timecho.com/docs/img/sync_en_02.png)
 
+V1.3.1 and later versions:
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
+
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
 Provide the following SQL statements for state management of synchronization tasks.
 
 ### Create Task
@@ -122,7 +133,7 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
index 122b60202..70f13d7c4 100644
--- a/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
+++ b/src/UserGuide/latest/User-Manual/Data-Sync_apache.md
@@ -92,7 +92,9 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
-![](https://alioss.timecho.com/docs/img/sync_en_02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
 
 Provide the following SQL statements for state management of synchronization tasks.
 
@@ -120,7 +122,7 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
index 83a5aacbe..a54752c69 100644
--- a/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
+++ b/src/UserGuide/latest/User-Manual/Data-Sync_timecho.md
@@ -94,7 +94,9 @@ The schema and auth synchronization functions have the following limitations:
 
 Data synchronization tasks have three states: RUNNING, STOPPED, and DROPPED. The task state transitions are shown in the following diagram:
 
-![](https://alioss.timecho.com/docs/img/sync_en_02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync02.png)
+
+After creation, the task will start directly, and when the task stops abnormally, the system will automatically attempt to restart the task.
 
 Provide the following SQL statements for state management of synchronization tasks.
 
@@ -122,7 +124,7 @@ WITH SINK (
 
 ### Start Task
 
-After creation, the task will not be processed immediately and needs to be started. Use the `START PIPE` statement to start the task and begin processing data: 
+Start processing data:
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md
index 8a89c377e..5c5e19c0c 100644
--- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_apache.md
@@ -91,7 +91,9 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
-![](https://alioss.timecho.com/docs/img/dataSync02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
 
 提供以下 SQL 语句对同步任务进行状态管理。
 
@@ -119,7 +121,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md
index 5d8fa9a91..ab2459659 100644
--- a/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/Master/User-Manual/Data-Sync_timecho.md
@@ -93,7 +93,9 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
-![](https://alioss.timecho.com/docs/img/dataSync02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
 
 提供以下 SQL 语句对同步任务进行状态管理。
 
@@ -121,7 +123,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
index 452c54961..f2d1bf5f7 100644
--- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_apache.md
@@ -91,8 +91,18 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
+V1.3.0及之前版本:
+
+在创建后不会立即启动，需要执行`START PIPE`语句启动任务。
+
 ![](https://alioss.timecho.com/docs/img/dataSync02.png)
 
+V1.3.1及之后版本:
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
+
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
 提供以下 SQL 语句对同步任务进行状态管理。
 
 ### 创建任务
@@ -119,7 +129,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
index ebba2dc10..b22db4067 100644
--- a/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/V1.3.0-2/User-Manual/Data-Sync_timecho.md
@@ -93,8 +93,18 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
+V1.3.0及之前版本:
+
+在创建后不会立即启动，需要执行`START PIPE`语句启动任务。
+
 ![](https://alioss.timecho.com/docs/img/dataSync02.png)
 
+V1.3.1及之后版本:
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
+
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
 提供以下 SQL 语句对同步任务进行状态管理。
 
 ### 创建任务
@@ -121,7 +131,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
index 8a89c377e..5c5e19c0c 100644
--- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
+++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_apache.md
@@ -91,7 +91,9 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
-![](https://alioss.timecho.com/docs/img/dataSync02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
 
 提供以下 SQL 语句对同步任务进行状态管理。
 
@@ -119,7 +121,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>
diff --git a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
index 5d8fa9a91..ab2459659 100644
--- a/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
+++ b/src/zh/UserGuide/latest/User-Manual/Data-Sync_timecho.md
@@ -93,7 +93,9 @@
 
 数据同步任务有三种状态：RUNNING、STOPPED 和 DROPPED。任务状态转换如下图所示：
 
-![](https://alioss.timecho.com/docs/img/dataSync02.png)
+![](https://alioss.timecho.com/docs/img/Data-Sync01.png)
+
+创建后任务会直接启动，同时当任务发生异常停止后，系统会自动尝试重启任务。
 
 提供以下 SQL 语句对同步任务进行状态管理。
 
@@ -121,7 +123,7 @@ WITH SINK (
 
 ### 开始任务
 
-创建之后，任务不会立即被处理，需要启动任务。使用`START PIPE`语句来启动任务，从而开始处理数据：
+开始处理数据：
 
 ```SQL
 START PIPE<PipeId>