Added the number of queuing tasks on the Task Record tab page in Running Record. Added two dimensions in the Failed indicator card, which are Construction Failed and Execution Failure.
Added Construction Failed in the drop-down list of Running Status on the Task Record page in Running Record.
Added the Specified Service Date setting item on the Retry page.
Added a xxx icon in the task record list in Running Record.
Disallowed the retrying of running or queuing instances.
Removed the Add Parameter function in the Parameter Setting step on the Retry page.
Supported the viewing of specific error stacks by clicking the number of dirty data rows generated by scheduled tasks.
Supported the Retry to This Node option on the Retry page.
Supported batch termination of scheduled tasks and batch deletion of running records.
Added a Reset button on the right side of the filter conditions above the task record list.
Recorded logs related to the reading and writing processes of scheduled tasks, as well as error and exception logs. Supported the exporting of task running records as files for viewing and usage. For details, see section "Export Record."
Supported the filtering of task running records by Record ID.
Blocked the Delete and Batch Delete functions for task running records, as the data storage location of task running records had been moved from FineDB to LogDB.
Displayed Triggering Method as API Call in the running records of scheduled tasks executed via API calls.
Supported the Retry Current Task and Downstream Item operation in Retry at Task Level on the Retry page.
4.2.1.1
Changed the Running Status filter from the form of a drop-down box to a checkbox group laid out flat on the page.
The Running Record page has two tab pages, namely Task Record and Running Plan.
The Task Record tab page displays the running information of scheduled tasks executed in Production Mode, including task running status, time consumption, triggering methods, and other information.
The Running Plan tab page displays the running information of all scheduling plans, as shown in the following figure.
Choose O&M Center > Scheduled Task > Running Record and select a specific task or folder to view the corresponding running information, including running status, time consumption, and triggering method, as shown in the following figure.
1. You can filter tasks by running status (with multi-selection supported.), triggering method, and dirty data. You can also search for tasks by Task Name or Record ID.
If dirty data is generated during the execution of a scheduled task, the number of dirty data rows will be displayed, as shown in the following figure.
2. You can filter the last-time/full records or running records within a custom period, as shown in the following figure.
1. Click View Details on the Task Record page to view the running log of the current task execution, as shown in the following figure.
If dirty data is generated during task execution, click Statistics to view the dirty data details. You can also filter the dirty data by Error Type and view the error details, as shown in the following figure.
2. The node execution status is displayed in the lower right corner of the node. You can hover your mouse over the node to view the node execution logs, as shown in the following figure.
For the running tasks, you can view the real-time running status on the Log tab page, as shown in the following figure.
You can customize the fields displayed in the table header and their order (You cannot modify the Task Name, Running Status, and View Details fields.), as shown in the following figure.
1. Assume the data fetching logic in a scheduled task is to fetch data within 24 hours preceding the scheduling time each day and collect the data into the target database.During a three-day holiday, the system crashed and the scheduled task did not run, resulting in a lack of data for those three days in the target database.
2. During the execution of a scheduled task, dirty data was generated in an output component. After the dirty data threshold was reached, the scheduled task did not stop. After the task execution was complete, the O&M personnel received a notification about the generation of dirty data.
The O&M personnel opened the dirty data processing page to check the reasons for the generation of dirty data. They found that the reason for the generation of dirty data was that the field length exceeded the limit. After modifying the field length at the target end, they hoped to rerun the task.
1. Two retry entries are available:
You can click the icon in the task record list in Running Record.
After clicking the View Details button, you can click the Retry button in the upper right corner of the Log page of the current task.
2. After you click the icon or the Retry button, the page is displayed as shown in the following figure.
Two retry methods are available: Retry in Specified Range and Retry at Task Level.
After selecting a node name in Retry in Specified Range, you can select Retry Node, Retry Node and Its Downstream Node, or Retry to This Node below.The setting page is shown in the following figure.
The following table describes the setting items.
Retry Node
1. Applicable scenario: An independent node fails to run and has no significant relationship with other nodes. For example, an Invocation Task node fails to run.
2. Function description: This option is only available when you select Retry in Specified Range. You can select a node where dirty data is generated and rerun the node. The execution granularity is at the node level, so you cannot specify the operators within a Data Transformation node to be rerun.
3. The Remark node is not displayed during the rerun.
Retry Node and Its Downstream Node
1. Applicable scenario: You have decomposed a business loop into multiple nodes, such as Node A (a Parameter Output node) and Node B referencing Node A. In this case, an error occurs and you need to rerun Node A and Node B.
2. Function description: This option is only available when you select Retry in Specified Range. You can select a node where dirty data is generated and rerun this node and its downstream nodes. (The execution results depend on the node's execution status and the execution status of nodes connected to it.)
The execution granularity is at the node level, so you cannot specify the operators within a Data Transformation node to be rerun.
3. If you select a Conditional Branch node, Parameter Assignment node, or Virtual Node, you can only select Retry Node and Its Downstream Node as Retry Method.
Retry to This Node
For details, see Running to This Node.
Parameter Setting
On the Retry page, you can temporarily configure parameters for this retry. The configuration result only affects the execution of this retry and does not modify any actual task configuration.
The setting page is shown in the following figure.
1. Specified Service Date:
Applicable scenario: In a scheduled task, you have used a custom time parameter aa, and its value is in the format of yyyy-mm-dd. An instance that was originally scheduled to run at 16:30:00 on November 1, 2023, failed to run due to network issues. Two days later, you want to rerun the task. You can set Specified Service Date to 2023-11-01 hh:mm:ss. (Since the parameter value is in the format of yyyy-mm-dd, you can customize the hh:mm:ss part.) In this case, the task will be rerun with the value of aa set to 2023-11-01.
The default value is the original scheduled start time of the instance, as shown in the following figure.
Specified Service Date can be left empty. If you leave it empty, it is equivalent to manually running the task.The value set in Specified Service Date is assigned to the built-in parameter ${cyctime} and custom time variables derived from ${cyctime}.
2. Static Parameter of Task:
Supports modification.
Modifying date-type parameters to constant parameters is not supported. Value format: ${Time format + N} or ${Time format - N}. Time format: a free combination of yyyy, yy, mm, dd, hh, mi, and ss.
Task A depends on Task B. If you set Specified Service Date for Task B, the execution of Task A will be triggered, but the execution time will be the current time, not the specified service date.
Retry Current Task
The scheduled task fails entirely. Retry the entire task.
Retry Current Task and Downstream Item (available in FineDataLink of V4.1.11.1 and later versions)
Description:
When configuring an event-based scheduling plan for Task A, if you set Task B as its downstream task, you can select Retry Current Task and Downstream Item when retrying Task A. The system will determine whether to trigger the execution of Task B based on the task relation and condition content configured in Event-Based Scheduling.
Application scenario:
Task A and Task B are upstream tasks of Task D. If both Task A and Task B run successfully, the execution of Task D will be triggered. You may want to rerun Task A and Task B when both tasks fail. In this case, you can use this function.
For details, see section "Retry in Specified Range."
Full synchronization
/
No
Incremental synchronization - using timestamps
Dynamic parameter: For example, you can configure now-1 as the data range to update data of the previous day each time.
Yes
During retry, you can specify temporary task parameter values for this execution.
Your task design needs to support idempotence, meaning that scheduled tasks for the same data range must support multiple runs.
Obtain the latest data timestamp from the target table.
For example, during each execution, the task first retrieves the maximum timestamp from the target table and uses it as the starting time for this synchronization.
You need to manually delete data in the target table that exceeds the size of this batch to perform a retry.
Customize table storage breakpoints.
For example, in each execution, the task stores the maximum timestamp of this synchronization in a table as the last step.
You need to manually modify breakpoint values for retry purposes.
Full table comparison
After retry, the running status of the original instance remains unchanged. The new retry instance will be associated with to the original instance, as shown in the following figure.
After clicking View Original Record, you can click the Retry Record button, and select a specific retry record to view its details, as shown in the following figure.
For FineDataLink of V4.1.7.3 and later versions, exporting running records as files is supported for viewing and usage.
1. You can terminate scheduled tasks and delete running records in batches.
Select the running records to be deleted or the instances to be terminated, and click the Batch Delete/Batch Terminate button, as shown in the following figure.
You can select all tasks on the current page with one click and terminate the tasks or delete their running records in batches.
Batch Terminate: Allows you to terminate running instances in batches. Terminating instances with execution/construction failure and instances that are interrupted or successful is not supported.
Batch Delete: Allows you to delete running or queuing instances.
2. After you click Batch Terminate/Batch Delete, you will be informed of the execution result, as shown in the following figure.
1. The Running Plan tab page displays the running information of all scheduling plans, as shown in the following figure.
2. You can click the View Details button to view the running records of the scheduled tasks configured with the corresponding scheduling plan, as shown in the following figure.
3. You can click the xxx icon to jump to the Scheduling Plan page where you can modify or delete the configured scheduling plans, as shown in the following figure.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy