DataWorks:Successful tasks with no output

Scenario 1: An auto triggered node is successfully run and has operational logs

When this applies: The node shows a success status and operational logs are present, but downstream tables have no data, or an error indicates that partitions of the ancestor node's output table do not exist.

The node's code logic runs successfully, but its scheduled instances fail to get data from ancestor nodes because the expected partitions are missing. Manually rerunning the instances can successfully retrieve ancestor node data.

Two dependency issues cause this:

1. Missing dependency — The auto triggered node does not depend on the ancestor nodes that generate the output table. Add the missing dependency.

2. Incorrect scheduling cycle — The auto triggered node depends on the correct ancestor nodes, but the partitions of the output table do not match what is expected. This indicates that the scheduling cycle of the depended instances is configured incorrectly. To diagnose this, open the General tab of the auto triggered node, or click the node and then click View Logs. The page shows the parameter values for ancestor and descendant nodes across a day, which lets you verify whether the partition dates align. Reconfigure the dependencies between nodes and confirm that the parameter values for ancestor and descendant nodes are correct.

   

   

Scenario 2: An auto triggered node is successfully run but has no operational logs

When this applies: The node shows a success status but no operational logs are generated.

Check the node status on the General tab. The absence of operational logs typically indicates a dry-run. For more information, see Why dry-runs occur.