Description of a node dry-run
For a node that is scheduled by week, month, or year, the scheduling system runs the node at the scheduling time in each scheduling cycle. On days when the node is not scheduled to run, a dry-run is performed on the node, and no data is generated. The following content describes the effects of a dry-run:
The scheduling system directly returns a success response, and the running duration is
0seconds.No run logs are generated.
The descendant nodes are not affected.
No resources are occupied.
Dry-run scenarios
A dry-run is triggered on an instance in various scenarios and generates no data.
Scenario 1: An instance is scheduled to run on a specific day of each week or month
Configure the scheduling settings for the instance that you want to run on a specific day of each week or month.
Double-click the node for which you want to configure the scheduling settings. In the right-side navigation pane of the configuration tab of the node, click Properties. On the Properties tab, click Scheduling Time to go to the Scheduling Time section.
Scheduling Cycle: Set this parameter to Week or Month.
Custom Time: Set this parameter to a specific day of each week or month.
Scheduling Time: Set this parameter to
10:10.
After the configuration is complete, save and deploy the node.
After you schedule the node to run on a specific day of each week or month, the node is run only at the scheduling time on the specified day of each week or month and generates data. On days when the node is not scheduled to run, dry-run instances are generated, and the node is not actually run. The status of the instances generated for the node is dry-run.
To prevent the generation of dry-run instances when you backfill data for a node scheduled by week or month, you must change the data timestamp for your data backfill task. For example, if a node is scheduled to run on the first day of every month, you must set the data timestamp to the last day of the previous month for the node when you backfill data for the node. You must perform the same configuration for a node scheduled by week.
Scenario 2: An instance is generated in real time but is expired
Scenario 3: The status of an instance is set to successful
If the status of an instance is Failed, you can perform the following operations to change the status of the instance: Go to Operation Center. In the left-side navigation pane of the Operation Center page, choose in the Node O&M section, find the instance whose status you want to change, and then choose More > Set Status to Successful in the Actions column. This way, the instance does not generate data or block the running of the descendant instances. The status of the instance is Instance Set Successfully.
Scenario 4: The property of an instance is dry-run
Double-click the node for which you want to configure or change the scheduling settings. In the right-side navigation pane of the configuration tab of the node, click Properties. On the Properties tab, click Scheduling Policies to go to the Scheduling Policies section. In this section, set the Scheduling Type parameter to Dry-run.
Check whether the status of the instance is dry-run.
Scenario 5: An instance is not selected for a temporary workflow
Configure the settings for the instance that is not selected for a temporary workflow.
In the upper-left corner of the current service page, click the
icon and choose . In the left-side navigation pane of the Operation Center page, choose .
On the page that appears, select an auto triggered node and backfill data for the node and its descendant nodes to generate a temporary workflow.
For example, Node C depends on Node B, and Node B depends on Node A. If you want to backfill data for Nodes A and C, the status of Node B is Unselected Instance in Temporary Workflow.
Troubleshoot dry-runs for nodes that are scheduled to run on a daily basis
If a node is scheduled to run on a daily basis, check whether Scheduling Type is set to Dry-run for the node in the Scheduling Policies section on the Properties tab.
T+1: indicates that the scheduling system runs nodes on the next day by using the data that is generated on the current day.