DataWorks:Dry-run

• Configure a weekly or monthly node.

  1. Double-click the task node. Click the Scheduling Settings button on the right to open the scheduling properties pane. Switch to the Time Properties module.

     • Scheduling Frequency: Set to Week or Month.

     • Specified time: Set to a specific day of the week or a specific day of the month.

     • Scheduling time: Set to 10:10.

     Set Effective date to Permanent.

  2. After you complete the configuration, save and deploy the node.

• When an auto triggered node is configured to run on a specific day of the week or a specific day of the month, it only runs and produces data at the specified time. On all other days, the system generates a dry-run instance.

To avoid dry-runs when you perform a data backfill for a scheduled node, you must set the business date correctly. For example, if a monthly node is scheduled for the 1st of each month, set the business date to the last day of the previous month for the data backfill. The same logic applies to weekly nodes.

• Configure an expired instance to be generated in real time.

  1. Double-click the node to configure or modify its scheduling cycle. On the right, click Scheduling Settings to open the scheduling properties panel, and go to the Scheduling Time section.

     Scheduling Frequency: Set to Daily.

     Scheduling time: Set to 10:09.

  2. Save and deploy the node. The deployment time is 10:00.

• When using the Instantly generate instances after the deployment option, an instance for an auto triggered node processes data only if deployed at least 10 minutes before its scheduled time. Otherwise, it becomes a dry-run instance. Its status is set to Expired instance generated in real-time. After you save and deploy, you can check the node's properties in Operation Center. The Instance Status is Expired instance generated in real-time, and the Scheduling Type is Real-time to Expired Instance Task.

If an instance fails, you can manually mark it as successful to unblock its descendant nodes. This action does not run the task or generate data. To do this, go to Operation and Maintenance Center > Auto Triggered Task O&M > Cycle Examples, find the failed instance, click More in the Actions column, and select Set to Successful. The instance's Instance Status then changes to Instance Set Successfully, with a run duration of 0s.

• Double-click the node to open its configuration panel. On the right, click Scheduling Settings and go to the Scheduling Policies section. Manually set the Scheduling Type to Empty Run Scheduling.

• The state of the instance is Dry Run by Instance Properties. After the configuration is complete, for the auto-triggered instances generated by this task, the Scheduling Type is displayed as Dry-run Task and the Instance State is displayed as Dry Run by Instance Properties in the task property details. The runtime of these instances is 0s.

• Configure an unselected instance in a temporary workflow.

  1. Click the icon and navigate to the All Products > Data Development and O&M > Operation and Maintenance Center (Workflow) page.

  2. In the Operation Center left navigation pane, choose Auto Triggered Task O&M > Auto Triggered Task to go to the list of auto triggered nodes.

     Find the target node, click Backfill Data in the Actions column, and select Current and Descendant Nodes from the drop-down menu.

  3. Select the auto triggered node and perform a data backfill for the current and descendant nodes to generate a temporary workflow.

     When you perform a data backfill, assume node C depends on node B, and node B depends on node A. If you backfill data for nodes A and C only, the instance for node B will have the status Unselected Instance in Temporary Workflow. After the temporary workflow is generated, open the Properties page for the corresponding backfill instance. You will see that the Instance Status is Unselected Instance in Temporary Workflow, the Instance Type is Backfill Instance, and the Task Status is Succeeded.