Undeploying a node removes it from the development environment and publishes the deletion to the production CDN mapping system. After a node is undeployed, it can no longer be scheduled. This topic uses a standard mode workspace as an example to describe how to undeploy a recurring node, restore the node, and how the platform handles existing and running instances after the node is undeployed.
Usage notes
-
To ensure that downstream tasks run as scheduled, DataWorks lets you undeploy only nodes that have no downstream dependencies. If a node has downstream dependencies, an error occurs. For more information, see Error: The node has child nodes, causing the task to fail to be deleted or undeployed. To view the dependencies of a node, see Manage recurring tasks.
-
If you undeploy a task from the Recurring Tasks page of the Operation Center in the production environment, the task reverts to an editable state in the development environment. It is not moved to the recycle bin. You can search for the node by its name in Data Studio.
Undeploy a task
The following procedure describes how to undeploy a recurring task.
Step 1: Delete the task from the development environment
Delete the task in Data Studio.
|
Operation type |
Description and illustration |
|
Delete a single task |
You can delete a specific task from the business process folder or the business process pane. After you delete the task, commit ( |
|
Delete tasks in batches |
You can use the Batch Operations feature to delete tasks in batches. |
|
Delete tasks using a node group |
You can select multiple nodes to create a node group and then delete the specified nodes. You can also delete nodes from an existing node group. After you delete the nodes, commit ( |
) the current business process.
Step 2: Publish the undeploy operation to the production environment
After you delete a task in Data Studio, DataWorks creates a pending undeploy record on the page. A user with Workspace Admin or O&M permissions must publish this record to the production environment. The task is undeployed from the production environment only after the record is successfully published. The publishing process may involve process controls. Ensure that the publish operation is successful. For more information about the publishing process and permission controls, see Publish a task.
Step 3: Confirm that the production task is undeployed
On the page, check whether the node exists. If the node does not exist, the task is successfully undeployed.
Impact of undeploying a task on existing instances
-
Instances that have not run
During the undeploy operation, a dry-run is performed for instances that have not yet run. The instance status is set to successful, but the task code is not executed. In a pay-as-you-go scenario, you are not charged instance fees for dry-run instances.
-
Running instances
Instances that are already running are not affected by the undeploy operation and continue to run as normal.
-
DataWorks does not support manually deleting instances. Instances are automatically deleted after they expire, which is typically after about 30 days.
-
If a recurring task does not need to run on a specific day, you can freeze the recurring instances generated for that day. If a task does not need to run for a long period, you can freeze the recurring task. For more information, see Basic O&M operations for recurring tasks.
Restore a task
You can restore the last 100 deleted tasks from the Recycle bin in Data Studio and then commit and publish them again.
-
A new node ID is generated after the node is restored.
-
You can restore only tasks, such as nodes, resources, and functions, that have been deleted from both the development and production environments. Otherwise, the Error: Publish the file ${filename} to the production environment or cancel the publishing operation in the publishing center first error occurs.
FAQ
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.