This topic describes how to configure the time properties of a node, including the instance generation method, rerun properties, and scheduling cycle.

Go to the Properties panel

  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Workspaces.
  3. After you select the region where the required workspace resides, find the workspace and click Data Analytics.
  4. On the Data Analytics tab of the DataStudio page, double-click a workflow in the left-side navigation pane.
  5. Click the Properties tab in the right-side navigation pane. The Properties panel appears. In this panel, you can configure time properties for the node in the Schedule section.
    Schedule section

Configure an instance generation method

You can use the Start Instantiation parameter to configure an instance generation method for the node. This parameter supports the following values:
  • Next Day: If you select this option, instances are generated in full mode.
    • If the node is committed and deployed before 23:30, the system starts to generate instances the next day.
    • If the node is committed and deployed after 23:30, the system starts to generate instances the day after the next day.
  • 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.

Configure parameters related to the node status

  • Normal: If you select this option, the node is run based on the setting of the Instance Recurrence parameter. By default, this option is selected for a node.
  • Dry Run: If you select this option, the node is run based on the setting of the Instance Recurrence parameter. However, the scheduling system does not actually run the node but directly returns a success response.
  • Rerun: Select a rule for rerunning the node as required. Valid values: Allow Regardless of Running Status, Allow upon Failure Only, and Disallow Regardless of Running Status.
    Note
    • Before you commit the node, make sure that the Rerun parameter is configured.
    • If you set the Rerun parameter to Disallow Regardless of Running Status, the Information message appears. Click OK.
  • Auto Rerun upon Error: specifies whether to automatically rerun the node if an error occurs. This parameter is available only when the Rerun parameter is set to Allow Regardless of Running Status or Allow upon Failure Only. If you select this check box, you can further specify the maximum number of automatic reruns and a rerun interval.
    • Number of automatic reruns with errors: specifies the maximum number of automatic reruns allowed after an error occurs. You can set this parameter based on your requirements. Valid values: 1 to 10. Default value: 3.
    • Error automatic rerun interval: specifies the interval at which automatic reruns are performed after an error occurs. You can set this parameter based on your requirements. Valid values: 1 to 30. Default value: 2. Unit: minutes.

    This parameter is unavailable if you set the Rerun parameter to Disallow Regardless of Running Status. In this case, the node is not rerun after an error occurs.

  • Start and End Dates: specifies the period during which the node is automatically run. After the specified period ends, the node is not automatically run.
  • Skip Execution: If you select this check box, the node is run based on the setting of the Instance Recurrence parameter. However, the scheduling system does not actually run the node but directly returns a failure response. You can select this check box if you do not need to run the node for a period of time.

Configure a scheduling cycle

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

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 node but directly returns a success response. If you test a node that is run by week or generate retroactive data for the node, you must set the data timestamp to one day earlier than the scheduled time at which you want the node to run.

For an auto triggered node, its dependencies take priority over its time properties. The scheduling system does not immediately run a node instance at the scheduled time. The system first checks whether all its ancestor instances are successfully run.
Note
  • If not all its ancestor instances are successfully run at the scheduled time, the node instance is in the Not Running state.
  • If all its ancestor instances are successfully run before the scheduled time arrives, the node instance enters the Pending (Schedule) state.
  • If all its ancestor instances are successfully run at the scheduled time, the node instance enters the Pending (Resources) state.

For more information about how to configure cross-cycle dependencies for a node, see Cross-cycle dependencies.

You can set the Instance Recurrence parameter to Minute, Hour, Day, Week, or Month.
  • Minute: The node is automatically run once every N minutes within a specific time period every day.
    In the example shown in the following figure, the node is run every 30 minutes during the period from 00:00 to 23:59 every day.Scheduling by minute

    The interval must be 5 minutes at least. The time expression is automatically generated based on the time you select and cannot be modified.

  • Hour: The node is automatically run once every N hours within a specific time period every day. For example, a node is run once every 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 every hour during 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.
    Scheduling by hour
    In the example shown in the preceding figure, the node is automatically run every 6 hours during the period from 00:00 to 23:59 every day. In this case, the scheduling system automatically generates and runs instances for the node, as shown in the following figure.Generate and run instances
  • Day: The node is automatically run once every day. If you create an auto triggered node, the node is configured to run at 00:00 every day by default. You can set the time as required. In the example shown in the following figure, the time is set to 13:00.Scheduling by day
    • If you select the Scheduled At check box, 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 its ancestor instances are successfully run and the scheduled time has arrived. Both prerequisites are indispensable and have no specific chronological order.
    • If you clear the Scheduled At check box, the scheduled time of the node is randomly set by default. The time is in the range of 00:00 to 00:30.

    For example, you create 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.

    The scheduling system automatically generates and runs instances for the nodes based on the time properties of the nodes.Generate and run instances
  • Week: The node is automatically run at a specified time of specified days every week. On the other days, the scheduling system still generates instances to ensure the proper running of descendant instances. However, the scheduling system does not actually run the node or consume resources but directly returns a success response.Scheduling by week

    In the example shown in the preceding figure, the scheduling system runs the instances generated on Mondays and Fridays. However, it returns success responses without running the instances generated on Tuesdays, Wednesdays, Thursdays, Saturdays, and Sundays.

    The scheduling system automatically generates and runs instances for the node based on the preceding time properties.Generate and run instances
  • Month: The node is automatically run at a specified time of specified days every month. On the other days, the scheduling system still generates instances to ensure the proper running of descendant instances. However, the scheduling system does not actually run the node or consume resources but directly returns a success response.Scheduling by month

    In the example shown in the preceding figure, the scheduling system runs the instance generated on the first day of each month. However, it returns success responses without running the instances generated on the other days.

    The scheduling system automatically generates and runs instances for the node based on the preceding time properties.Generate and run instances

Configure a timeout period

You can use the Timeout time parameter to specify a timeout period. If the running time of a node exceeds the specified timeout period, it is automatically terminated.Timeout period
  • The timeout period is valid only for nodes that are run on shared resource groups for scheduling.
  • The timeout period applies only to auto triggered node instances, retroactive instances, and test instances.
  • The default timeout period ranges from 72 hours to 168 hours. The system automatically adjusts the default timeout period for a node based on system loads. You can customize a timeout period, but it cannot exceed 168 hours.