Real-Time Sync Task Operations and Maintenance

Overview

After a Real-time Sync task is created, it needs to be managed and maintained.

Manage Real-Time Sync Tasks

Real-Time Sync Task List

Users can edit, rename, and delete Real-time Sync tasks, and view task configuration details, task status, the latest run time, the latest modified time, and both running and historical task instances.

Real-Time Sync Task Status

Status	Description
Not Running	The task is in the `Not Running` state immediately after it is created.
Running	After you click run, the task enters the `Running` state.
Paused	A running task can be paused or stopped. A paused task records the pause time, and when it is run again, synchronization resumes from 30 minutes before the recorded pause time. Pay attention to log retention time. If the pause duration exceeds the retention period, data loss may occur because the required logs can no longer be found.
Stopped	After the task is stopped, it can be modified and then run again using the updated configuration.

Configure Notices

Go to the task details page and open the Notices tab to configure alerts for the Real-time Sync task.

Two alert types are supported: Task failure and Task exception.

Task failure: If a Flink synchronization task still fails after multiple retries, the task status changes to failed. If a failure alert is configured, a notification is sent.
Task exception: If the task becomes abnormal because of issues such as network fluctuations or sudden data spikes, but later recovers after the environment stabilizes, users may still want timely notifications during the abnormal period so they can intervene manually. In this case, enable the task exception alert so that a notification is sent immediately when an exception occurs.

Notification channels: DingTalk, Feishu, WeCom, E-mail, and custom channels are supported.

Recipients: Select the users who should receive the task alerts.

Notification title and content: Enter the Subject and Message body.