This topic describes the FAQ about scheduling properties.

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?

A node scheduled by day can depend on a node scheduled by hour. To enable Node B to automatically run every day after all 24 instances of Node A are run, do not specify the time to run Node B every day. Configure Node A as the parent node of Node B.

A node can depend on any other node, regardless of the recurrence. The recurrence of each node is specified in its scheduling properties.

Node A is run once per hour on the hour every day and Node B is run once per 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 scheduling properties of Node A, select Cross-Cycle Dependencies and select Instances of Current Node from the Depend On drop-down list. When you configure the scheduling properties of Node B, configure Node B to depend on Node A and set the scheduled time of Node B to 00:00 every day. In this way, instances of Node B only depend on the instance of Node A generated at 00:00 every day, that is, the first instance of Node A.

Node A is run once every Monday and Node B depends on 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. That is, select Week as the instance recurrence and select Monday.

How are the instances of a node affected when the node is deleted?

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

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

No, DataWorks does not support setting a node to run on the last day of each month. If you enable 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 without running the code in any other month.

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

If a node scheduled by day depends on a node scheduled by hour, how do I enable the node scheduled by day to run at 00:00 every day?

You can configure the node scheduled by day to depend on the data generated on the day before for the node scheduled by hour. If the node scheduled by day depends on the data generated on the current day for the node scheduled by hour, the instances of the node scheduled by day can be run only on the next day.

In the Schedule section of the node scheduled by day, select Cross-Cycle Dependencies, select Instances of Custom Nodes from the Depend On drop-down list, and then enter the ID of the node scheduled by hour on which the node scheduled by day depends. Commit and deploy the node scheduled by day.

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

You can set the cross-cycle dependency for the current node to depend on the last-cycle instances of the parent 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 have not been run. If the scheduling properties are modified, the modified configuration only applies to new node instances.