This topic covers common issues that arise when undeploying nodes in DataWorks, including how to confirm undeployment, restore undeployed nodes, and resolve errors.
Undeploy a node
In a standard-mode workspace, the development and production environments are isolated. Deleting a node in DataStudio removes it only from the development environment. To remove the node from the production environment, you must deploy this deletion. The node is considered undeployed only after the deployment succeeds.
For more information, see Undeploy a task.
Confirm node undeployment
After undeployment completes, go to Operation Center > Auto Triggered Nodes and verify that the node no longer appears in the list. The absence of the node confirms that the undeployment was successful.
Restore an undeployed node
Undeployed nodes are moved to the Recycle Bin. You can restore the undeployed node from the Recycle Bin. For details, see Restore a task.
Error: Pending deletion prevents restore
Cause: The Recycle Bin only supports restoring tasks — such as nodes, resources, or functions — that have been deleted from both the development and production environments. If a deletion was made in the development environment but not yet deployed to the production environment, the restore fails.
Resolution: Go to the task deployment page, cancel the node deletion operation, and then restore the file in DataStudio.
Error: Node has downstream nodes
Cause: DataWorks only allows a task to be undeployed if it has no downstream dependencies in either the development or production environment.
Undeploying a node may cause errors in dependent tasks. Before proceeding, contact the owners of all downstream tasks.
Resolution:
-
On the Auto Triggered Nodes page in Operation Center, identify all downstream dependencies in both the development and production environments. For details, see Manage auto triggered tasks.
-
For each downstream task, open its Properties page and remove the dependency on the node you want to undeploy. For details, see Delete or change scheduling dependencies between nodes.
-
Commit the downstream task to remove the dependency from the development environment.
-
Deploy the downstream task to remove the dependency from the production environment.
-
Undeploy the original node. For details, see Undeploy a task.