Problem description

After I commit a node, I cannot find the instance of the node in Operation Center.

Possible cause

The instance is not generated. The system generates an instance for your node based on the values of Start Instantiation and parameters in the Dependencies section. The instance may fail to be generated due to the following reasons:
  • The node is an isolated node because no dependent ancestor node is configured for the node. In this case, the system cannot generate an instance for the node.

    In most cases, this issue occurs if you delete the dependent ancestor node configured for the node before you commit the node. As a result, the node becomes an isolated node.

  • If you set Start Instantiation to Next Day, the system generates an instance at the following time points:
    • If you commit your node before 23:30, the system immediately generates an instance for the node. You can view the instance in the instance list of Operation Center on the following day.
    • If you commit your node after 23:30, the system generates an instance at 23:30 of the following day. You can view the instance in the instance list of Operation Center two days after you commit the node.
    You can view the instance of the node in the instance list of Operation Center only after the instance is generated.
  • If you set Start Instantiation to Immediately After Deployment, the system generates an instance at the following time points:
    Note You cannot set Start Instantiation to Immediately After Deployment for a node that is created in a workflow of DataWorks of an earlier edition.
    • If you commit your node after 23:30, the system does not generate an instance for the node. As a result, you cannot find the instance of the node in the instance list.
    • If you commit your node before 23:30, the system immediately generates an instance for the node. In this case, you can view the instance in the instance list.
      • If the scheduled time for running your node is 10 or more minutes later than the time you commit your node, the system generates an instance for the node and runs the node. Then, you can view the instance in the instance list. For example, you commit your node at 18:00, but your node is scheduled to run at 18:30. In this case, the preceding situation occurs.
      • If the scheduled time for running your node is less than 10 minutes from the time you commit the code, the system generates an instance whose running is complete for the node. The instance is an expired instance that is generated in real time. For example, you commit your node at 18:00, but your node is scheduled to run at 18:05. In this case, the preceding situation occurs.
    If you commit your node before 23:30, you can find the instance of the node in the instance list. However, you must check whether the instance is an expired instance.

Solution

  1. Check the parameter configurations in the Dependencies section to ensure that the node is not an isolated node.
    You must check whether dependent ancestor nodes are configured for the node in the Dependencies section of the DataStudio page.
  2. Check whether the node is committed before 23:30.
    You must check the time when the node is committed on the Deploy Tasks page. If the node is committed after 23:30, you can commit the node again before 23:30 on the following day.
    Note If you set Start Instantiation to Immediately After Deployment, you can check whether the scheduled time for running the node is 10 or more minutes later than the time you commit the node. If the interval is within 10 minutes, you must commit the node again and ensure that the interval is 10 or more minutes. Otherwise, an expired instance is generated for the node, and the node fails to be run.