This topic explains why an instance performs a dry run.
What is a dry run?
A dry-run instance is marked as successful but has an empty run log, shows no execution duration, and processes no data.
Why does an instance perform a dry run?
Scenario 1: Dry run for weekly/monthly cycle
Days of the weekDay of the monthDry run for weekly/monthly cycleIf a node is scheduled to run on or , it only processes data on the scheduled day. On all other days, the system generates a dry-run instance. The status of this instance is .
To ensure a cycle instance processes data, set its scheduled time to at least 10 minutes after the node is deployed. Alternatively, you can run a data backfill using the previous day's data timestamp. The cycle instance will then run normally on the following day.
Operation CenterCycle TaskCycle InstancePropertiesTo prevent a dry run when backfilling data for a weekly or monthly node, check the scheduled time and data timestamp of the cycle instance. For example, if a monthly node is scheduled for the 1st of each month, you must set the data timestamp to the end of the month for the data backfill. The same logic applies to weekly nodes. You can view these details in the panel by navigating to > > and selecting the target instance.
Scenario 2: Deprecated real time generated task
When you use the Immediately After Deployment option to generate a cycle instance, only instances scheduled to run more than 10 minutes after deployment will process data. For instances scheduled to run within 10 minutes of deployment, the system creates a dry-run instance instead. The status of this instance is Deprecated real time generated task.
Note For more information, see Generate an instance immediately after you deploy a node.
Scenario 3: Instance Set Successfully
Set as SuccessfulInstance Set SuccessfullyIf you use the option on a failed instance, its status changes to successful. However, the instance does not actually run or process data, and it no longer blocks any descendant nodes. The status of this instance becomes .
Scenario 4: Property is Dry Run
Dry-runProperty is Dry RunCheck the node's scheduling configuration in . If the time property is set to , the instance performs a dry run. The status of this instance is .
Scenario 5: Unselected instance in temporary workflow
Unselected instance in temporary workflowDuring a data backfill, assume a dependency chain where node C depends on node B, and node B depends on node A. If you create a temporary workflow to backfill data only for nodes A and C, the instance for node B is skipped. Its status becomes .
Troubleshooting daily node dry runs
If a daily node performs a dry run, check if a dry run is enabled in its scheduling configuration.
Note T+1 scheduling means that data with today's data timestamp is processed on the next day.
该文章对您有帮助吗？