DataWorks:Task succeeds but produces no data

This scenario occurs when a node runs successfully, but its scheduled instance fails to retrieve data from an upstream node or reports a missing table partition. However, rerunning the instance manually succeeds.

1. A dependency on the upstream node that produces the required data has not been configured.
2. A dependency exists, but the table partition from the upstream node does not match what the downstream node expects. This often indicates a misconfigured dependency. To diagnose the issue, compare the execution parameters of the upstream and downstream nodes in the instance logs.

Check the parameters for the upstream and downstream nodes. On the scheduled instance page in Operation Center, the DAG shows the upstream virtual node xc_demo_start connected to the downstream offline sync node xc_oss_data_sync. Select a node and view the Properties tab for details such as the data destination type (MaxCompute), runtime duration (40s), and instance status (Success). The execution parameter bizdate=20210614 sets the business date for this instance to 2021-06-14.