If a node is scheduled by year, the node is automatically run at a specified point in time on specific days every year.

Precautions

To ensure that the descendant instances of a node that is scheduled by year can be run as expected during the time period that is not the scheduled time of the node, the system generates dry-run auto triggered instances for the node. That means the scheduling system does not actually run the node but directly returns a success response when the scheduled time of the node arrives. This way, the descendant nodes of the node can be run as expected and resources are not occupied by the node.

Configuration example

  • Configuration method

    On the DataStudio page, create a node and go to the configuration tab of the node. Click the Properties tab in the right-side navigation pane. In the General section of the Properties tab, configure the scheduling period for the node.

  • Scenario
    • Configuration details
      If the node is scheduled to run at a specified point in time on the first and last days of January, April, July, and October each year, the scheduling system runs the instances that are generated on these days each year. The scheduling system generates dry-run instances for the node on each of the rest days in the year and directly returns a success response for the instances. The following figure shows the details about the configurations.
      Note The corn expression is automatically generated based on the time you select and cannot be changed.
      Schedule a node by year
    • Scheduling details
      The following figure shows that the scheduling system automatically generates and runs instances for the nodes. Schedule a node by year