This topic provides answers to some frequently asked questions about time properties.

Node A is an ancestor node of Node B. Node A is scheduled by hour and Node B is scheduled by day. How do I enable Node B to automatically run every day after all instances of Node A are run?

Node B depends on the instances of Node A that are generated on the current day. Node B automatically runs every day after all instances of Node A are run. If the last instance of Node A is run on the next day, Node B still runs, but at a time different from the configured one. Scheduling parameters are replaced as expected.

Node A runs every hour on the hour, and Node B runs once every day. How do I enable Node B to automatically run after Node A is run for the first time every day?

When you configure the time properties of Node A, select Cross-Cycle Dependencies and select Instances of Current Node from the Depend On drop-down list. Set Run At to 00:00 for Node B. This way, Node B depends on only the first instance of Node A that is generated at 00:00 every day.

Node A is run once every Monday and Node B depends on the instances of Node A. How do I enable Node B to run once every Monday?

Configure the scheduling properties of Node B to be the same as those of Node A. Select Week from the Scheduling Cycle drop-down list and Monday from the Run Every drop-down list.

What is the impact on the instances of a node after the node is deleted?

The scheduling system generates one or more instances for a node every day based on the time properties of the node. If the node is deleted after it is run for a period of time, its instances are retained. However, the instances will fail to run after the node is deleted. This is because the required code is unavailable.

How do I enable a node to process monthly data on the last day of each month?

DataWorks does not allow a node to run on the last day of each month. If you configure a node to run on the thirty-first day of each month, the scheduling system runs a node instance on that day of each month that has 31 days and returns a success response on other days after a node instance is generated.

We recommend that you configure a node to process data of the previous month on the first day of each month.

Node A is scheduled by hour and Node B is scheduled by day. Node B depends on the instances of Node A that are generated every day. How do I enable Node B to automatically run at 00:00 every day?

Solution:
  1. Double-click Node B on the DataStudio page in the DataWorks console.
  2. On the node tab that appears, click Properties in the right-side navigation pane.
  3. In the Schedule section of the Properties panel, select Cross-Cycle Dependencies, select Instances of Custom Nodes from the Depend On drop-down list, enter the ID of Node A in the field, and then set the Run At parameter to 00:00.
    Notice
    • Node B depends on only the instances of Node A that are generated on the previous day. If Node B depends on the instances of Node A that are generated on the current day, the instances of Node B will be run on the next day.
    • If Node B depends on only the last instance of Node A that is generated on the previous day, Node A must depend on its last-cycle instances.
  4. Save the settings and commit Node B.

What do I do if I do not know when the output data of the ancestor node is generated?

You can select Cross-Cycle Dependencies for the current node.

After a modified node is committed and deployed to the production environment, will the existing faulty node instances in the production environment be overwritten?

No, the existing node instances will not be overwritten. The updated code is used to run the new node instances that are not run. If scheduling properties are modified, the modified configuration applies only to the new node instances.

The node whose Rerun is set to Allow Regardless of Running Status or Allow upon Failure Only does not rerun after it fails to run, and the error message "Task Run Timed Out, Killed by System!!!" appears. What do I do?

  • Problem description: The Rerun parameter in the Schedule section of the Properties tab is set to Allow Regardless of Running Status or Allow upon Failure Only for the node. However, the node does not rerun after it fails to run and the error message "Task Run Timed Out, Killed by System!!!" appears.
  • Cause: The Timeout time parameter is configured in the Schedule section of the Properties tab. If the running duration of the node exceeds the value of the Timeout time parameter, the node automatically terminates and does not rerun.
  • Solution: Manually enable the node to rerun in this scenario.

If the Number of automatic reruns with errors parameter is set to 1 for the node, the node does not rerun after it fails to run. What do I do?

  • Problem description: In the Schedule section of the Properties tab, the Number of automatic reruns with errors parameter is set to 1 for the node. However, the node does not rerun after it fails to run.
  • Cause: The setting of the Number of automatic reruns with errors parameter does not trigger the node to rerun after it fails to run. If you set the Number of automatic reruns with errors parameter to n for a node, the node is rerun n - 1 times. By default, the Number of automatic reruns with errors parameter is set to 3. The minimum value is 1 and the maximum value is 10. 1 specifies that a node is not rerun when an error occurs. 10 specifies that a node is rerun nine times when an error occurs. You can change the parameter value based on your business requirements.
  • Solution: To enable the node to rerun once after it fails to run, set the Number of automatic reruns with errors parameter to 2.