Task Control - Result Notification- FineDataLink Help Document

Last update: April 23, 2025

Overview

Version

FineDataLink Version	Functional Change
4.1.4	Added Save and Cancel buttons for you to confirm or discard your edits.
4.1.5.4	Supported notification of changes in source table structures for scheduled tasks.
4.1.5.5	Supported notification of instance construction failure.

Function Overview

With Result Notification enabled, the platform will notify the relevant personnel in case of task execution failure.

The notification channel includes platform messages, emails, SMSs, DingTalk chatbots, Lark chatbots, and WeCom chatbots.
The notification content includes task exceptions, dirty data, and source table structure changes.

Note:

The Result Notification configuration of a scheduled task takes effect only when you publish the task to Production Mode.

1.2.png

Prerequisite

To notify users via email or SMS, you need to finish corresponding configuration on the platform first. For details, see Email and SMS.

Function Description

With Result Notification enabled, the platform will notify the relevant personnel in case of task execution failure.

The Result Notification function is disabled by default and needs to be enbaled manually.

You need to note the following points:

1. Notification messages are sent only in case of task execution failure. Successful execution triggers no notification.

2. The failure notification of a single scheduled task is sent at most once within 10 seconds.For example:

Task A is configured with Task Failure Reminder and Dirty Data Notification. At 10:00:00, the task execution stops as the dirty data threshold is exceeded.Between 10:00:00 and 10:00:09.999, if Task A is triggered again and the execution stops again for the same reason, the notification message will not be sent again.During the same period, if Task B stops execution as the dirty data threshold is exceeded, notification will be triggered. (This is because Task A and Task B are different tasks.)

3. In FineDataLink of V4.1.5.5 and later versions, notification will also be triggered by instance construction failure. For example, if Notification Channel is set to Platform, a platform message will be sent in case of instance construction failure, as shown in the following figure.

Result Notification

Result Notification is disabled by default and needs to be enabled manually.

Notification Content

Task Exception Notification

Task Failure Reminder is selected by default and cannot be deselected.

In independently deployed FineDataLink projects, the notification content for all channels is standardized as "Task name failed to run, which started to be executed at 2023-03-21 15:22:38 and ended at 2023-03-21 15:22:41. View details under O&M Center > Scheduled Task > Running Record.”

Specific Error Info:

It is deselected by default. If you select this item, the error information will be sent in case of task execution failure.

The notification content for all channels is standardized as:

"Task name failed to run, which started to be executed at 2023-03-21 15:22:38 and ended at 2023-03-21 15:22:41. The error node is Node name and Specific error information.For more error reports, view details under O&M Center > Scheduled Task > Running Record."

The following is an example of error messages.

2.2.1.png

If multiple nodes fail to run, the notification content for all channels is standardized as:

Dirty Data Notification

1. Dirty Data Occurrence: If you select Dirty Data Notification, Dirty Data Occurrence is selected by default.Notification will be triggered when dirty data occurs during the execution of scheduled tasks.

2. Dirty Data Summary: If you select Dirty Data Summary, the dirty data will be summarized by generation reason and the statistics will be sent to the notification object after the scheduled task completes.

3. The following table displays the specific error information.

Dirty Data Summary Unticked	Dirty Data Summary Ticked
Title: Dirty Data Notification for Data Development Task [Info Platform] Hello. Dirty data is generated in the data development task Task name. The reason is Error reason. View details in the corresponding task log under O&M Center > Scheduled Task.	Title: Dirty Data Notification for Data Development Task Dirty data is generated in the data development task Task name. The reason is Error reason. View details in the corresponding task log under O&M Center > Scheduled Task. The error reason composition is described below. 「Error reason one-Count Record(s)」 & 「Error reason two-Count Record(s)」 & 「Error reason three-Count Record(s)」 Up to the first three reasons are displayed, and the reasons are sorted in descending order by the number of dirty data records. When the number of reasons exceeds three, the error message is: 「Error reason one-Count Record(s)」 & 「Error reason two-Count Record(s)」 & 「Error reason three-Count Record(s)」and others Example:

Dirty Data Summary Unticked

Dirty Data Summary Ticked

Title: Dirty Data Notification for Data Development Task

[Info Platform] Hello. Dirty data is generated in the data development task Task name. The reason is Error reason. View details in the corresponding task log under O&M Center > Scheduled Task.

Title: Dirty Data Notification for Data Development Task

Dirty data is generated in the data development task Task name. The reason is Error reason. View details in the corresponding task log under O&M Center > Scheduled Task.

The error reason composition is described below.

「Error reason one-Count Record(s)」 & 「Error reason two-Count Record(s)」 & 「Error reason three-Count Record(s)」

Up to the first three reasons are displayed, and the reasons are sorted in descending order by the number of dirty data records. When the number of reasons exceeds three, the error message is:

「Error reason one-Count Record(s)」 & 「Error reason two-Count Record(s)」 & 「Error reason three-Count Record(s)」and others

Example:

2.2.2-2.png

4. The Statistics tab page displays the number of dirty data rows of different statistics objects. You can click the number of dirty data rows to view the row count of dirty data caused by different reasons.

Notification of Source Table Structure Change

You can select Notification of Source Table Structure Change under Task Control > Result Notification to ensure the notification of the DDL changes in the source table of a scheduled task.The notification will be triggered when DDL changes occur in the source table of a running task, as shown in the following figure.

Classification	Description
Prerequisite	You have selected Table Selection as Configuration Method on the Data Source tab page in the Data Synchronization node. You have enabled DDL Change Detection on the Data Destination and Mapping tab page.
Scope of Effect	Detectable changes in the source table structure include field adding and deletion, field renaming, and changes in field types and lengths.
Notification Content	Title: Notification of Timed Synchronization of Source Table Structure Change Content: In the Task name scheduled task, the structure of the source table of the Node name node Table name has changed. Check details in the corresponding task log in Task O&M > Scheduled Task. If you select Platform as Notification Channel, the title will be omitted.

Classification

Description

Prerequisite

You have selected Table Selection as Configuration Method on the Data Source tab page in the Data Synchronization node.

You have enabled DDL Change Detection on the Data Destination and Mapping tab page.

Scope of Effect

Detectable changes in the source table structure include field adding and deletion, field renaming, and changes in field types and lengths.

Notification Content

Title: Notification of Timed Synchronization of Source Table Structure Change

Content:

In the Task name scheduled task, the structure of the source table of the Node name node Table name has changed. Check details in the corresponding task log in Task O&M > Scheduled Task.

If you select Platform as Notification Channel, the title will be omitted.

2.2.3-1.png

2.2.3-2.png

Platform User Group

When Notification Channel is set to SMS/Email/Platform, you can configure notification objects (including users, departments, and roles) based on the platform system. Ultimate objects would be the union of the selected.

Notification Channel

General Explanation:

1. When you select SMS/Email/Platform as Notification Channel, you need to select Platform User Group as Notification Object, as shown in the following figure.

2.4-1.png

2. When you select SMS/Email as Notification Channel, Custom Recipient and Platform User Group cannot be left empty at the same time.

3. When you select SMS/Email as Notification Channel, you cannot reference parameters in Custom Recipient.

4. If you select SMS/Email as Notification Channel, select the user A in Platform User Group, and set Custom Recipient to the mobile number or the email address of the user A, the notification will be sent via one channel only.

Specific Explanation:

If you set Notification Channel to Client, you can set Notification Object to DingTalk/Lark/WeCom.

Note:

You are not allowed to enter multiple Webhook addresses for a single notification channel.

2.4-2.png

For details about the Webhook URL of a DingTalk chatbot, see the official document.

For details about the Webhook URL of a Lark chatbot, see Custom Bot Usage Guide.

Webhook URL of a WeCom chatbot: The following figure shows the steps for adding a chatbot. After the chatbot is successfully added, the Webhook URL will be displayed on the prompt page.

2.4-3.png