This topic describes how to configure the scheduling properties of a node, including the recurrence and dependencies.

You can click the Properties tab in the right-side navigation pane of the node configuration tab and set the parameters in the Schedule section.

Instance generation methods

  • Next Day: If you select this option, instances are generated in full mode.
    • If the node is committed and deployed before 23:30, instances are generated from the next day.
    • If the node is committed and deployed after 23:30, instances are generated from the day after tomorrow.
  • Immediately After Deployment: If you select this option, instances are immediately generated after the node is committed and deployed. For more information, see Immediate instance generation.

Node status

  • Normal: If you select this option, the node is run based on the recurrence. By default, this option is selected for a node.
  • Dry Run: If you select this option, the node is run based on the recurrence. However, the scheduling system does not actually run the code but directly returns a success response.
  • Rerun: Valid values are Allow Regardless of Running Status, Allow upon Failure Only, and Disallow Regardless of Running Status. You can select an option as required.
    Note
    • If you do not set the Rerun parameter, you cannot commit the node.
    • If you select Disallow Regardless of Running Status, you must click OK in the Information dialog box that appears.
  • Auto Rerun upon Error: You can select this check box if you set Rerun to Allow Regardless of Running Status or Allow upon Failure Only. After you select this check box, the node automatically reruns when an error occurs. If you set Rerun to Disallow Regardless of Running Status, this check box does not appear. In this case, the node does not rerun when an error occurs.
  • Start and End Dates: You can specify the start date and end date to automatically run the node within the specified period based on the configured scheduling properties. After the period expires, the node is not automatically run.
  • Skip Execution: If you select this check box, the node is run based on the recurrence. However, the scheduling system does not actually run the code but directly returns a failure response. You can select this check box if you want to suspend a node and run it later.

Recurrence

After a node is committed and deployed, the scheduling system generates instances every day from the next day based on the scheduling properties of the node. Then, the scheduling system runs the instances based on the running results of ancestor instances and the scheduled time. If a node is committed and deployed after 23:30, the scheduling system generates instances for it from the day after tomorrow.

For example, if you schedule a node to run every Monday, the node is run only on Mondays. On the other days, the scheduling system does not actually run the code but directly returns a success response. When you test a node scheduled by week or generate retroactive data for the node, you must set the data timestamp to one day earlier than the scheduled time to run the node.

For an auto triggered node, its dependencies take priority over other scheduling properties. That is, when the scheduled time arrives, the scheduling system does not immediately run a node instance but first checks whether all the ancestor instances are run.
Note
  • The node instance is in the Not Running state if any ancestor instances are not run when the scheduled time arrives.
  • The node instance is in the Pending (Schedule) state if the scheduled time does not arrive but all the ancestor instances are run.
  • The node instance is in the Pending (Resources) state if all the ancestor instances are run and the scheduled time arrives.

For more information about how to set the Cross-Cycle Dependencies parameter, see Cross-cycle dependencies.

You can set Instance Recurrence to Minute, Hour, Day, Week, or Month.
  • Nodes scheduled by minute are automatically run once every N minutes in a specific time period every day.

    For example, you have created a node. As shown in the following figure, the node is run every 30 minutes in the period from 00:00 to 23:59 every day.

    Currently, a minimum interval of 5 minutes is supported. The time expression is automatically generated based on the time you select and cannot be modified.

  • Nodes scheduled by hour are automatically run once every N hours in a specific time period every day. For example, a node is run once per hour from 01:00 to 04:00 every day.
    Note The time period is a closed interval. For example, if a node is scheduled to run once per hour in the period from 00:00 to 03:00, the scheduling system generates four instances every day, which are run at 00:00, 01:00, 02:00, and 03:00, respectively.

    For example, you have created a node. As shown in the preceding figure, the node is automatically run every 6 hours in the period from 00:00 to 23:59 every day. In this case, the scheduling system automatically generates and runs instances for the node.

  • Nodes scheduled by day are automatically run once per day. When you create an auto triggered node, the node is set to run at 00:00 every day by default. You can specify another time as needed. In the example shown in the following figure, the time is specified as 13:00.
    • If you select Customize Runtime, the node is run at the specified time every day. The time format is HH:MM.
      Note An auto triggered node can be run only when all the ancestor instances are run and the scheduled time arrives. Both prerequisites are indispensable and have no specific chronological order.
    • If you clear Customize Runtime, the scheduled time of the node is randomly set in the range of 00:00 to 00:30.

    For example, you have created an import node, an analytics node, and an export node. They are all scheduled to run at 13:00 every day. The analytics node depends on the import node, and the export node depends on the analytics node.

    Based on the preceding node scheduling properties, the scheduling system automatically generates and runs instances for the nodes, as shown in the following figure.Generate and run instances
  • Nodes scheduled by week are automatically run at a specified time of specified days every week. On the other days, the scheduling system still generates instances to make sure the proper running of descendant instances. However, the system does not actually run the code or consume resources but directly returns a success response.

    For example, you have created a node. As shown in the preceding figure, the scheduling system runs instances generated on Mondays and Fridays, but returns success responses without running the code for instances generated on Tuesdays, Wednesdays, Thursdays, Saturdays, and Sundays.

    Based on the preceding node scheduling properties, the scheduling system automatically generates and runs instances for the node, as shown in the following figure.Generate and run instances
  • Nodes scheduled by month are automatically run at a specified time of specified days every month. On the other days, the scheduling system still generates instances to make sure the proper running of descendant instances. However, the system does not actually run the code or consume resources but directly returns a success response.

    For example, you have created a node. As shown in the preceding figure, the scheduling system runs the instance generated on the first day of each month, but returns success responses without running the code for instances generated on the other days.

    Based on the preceding node scheduling properties, the scheduling system automatically generates and runs instances for the node, as shown in the following figure.Generate and run instances