DataWorks:Nodes that are successfully run but have no data generated

If an auto triggered node is successfully run, the code logic of the node is executed as expected. However, when the instances of the auto triggered node attempt to be run as scheduled, the node fails to obtain data of its ancestor nodes or an error is reported, indicating that the partitions of the output table of its ancestor nodes do not exist. You can manually rerun the instances to obtain data of the ancestor nodes.

1. The auto triggered node does not depend on its ancestor nodes that generates an output table.

2. The auto triggered node depends on its ancestor nodes that generates an output table. However, the partitions of the output table are not what are expected. This indicates that the cycle of the instances on which the auto triggered node depends is incorrect. On the General tab of the auto triggered node or on the page that appears after you click the auto triggered node and click View Logs, you can view the values of the parameters for the ancestor and descendant nodes of the auto triggered node in a day.

Check the values of the parameters for the ancestor and descendant nodes of the auto triggered node