All Products
Search

This Product

    DataWorks:Deploy a node

    Document Center

    DataWorks:Deploy a node

    Last Updated:Jul 11, 2026

    This topic describes how to deploy a node in a workspace that is in standard mode.

    Prerequisites

    • Make sure that the node is submitted before you deploy it.

    • Before you deploy a node, make sure that it is associated with compute resources. If the Compute Resource drop-down list in the schedule settings of the node is empty, go to the workspace management page to associate the required compute resources with Data Studio.

    Background

    In a basic mode workspace, a submitted node is deployed to the production environment and is automatically scheduled. In a standard mode workspace, a submitted node takes effect only in the development environment and is not automatically scheduled. You must use the deployment process to deploy the node to the production environment. After the node is deployed, it runs on a periodic schedule.

    Note

    All operations that you submit in Data Studio are sent to the deployment page and are in the pending deployment state. On this page, you can use the deployment process to deploy the operations to the production environment.

    1. DataWorks provides the following types of pre-deployment checks:

      • Code review: You can enable mandatory code review for a workspace. If this feature is enabled, a node cannot be deployed until it passes code review. For more information, see Code review.

      • Smoke testing: You can enable mandatory smoke testing for a workspace. If this feature is enabled, a node cannot be deployed until it passes smoke testing. For more information, see Perform smoke testing.

      • Extensions: You can enable extension validation for a workspace. If this feature is enabled, a node cannot be deployed until it passes extension validation. For more information, see Extensions overview.

      • Check items: You can enable checks for specific items in the Data Governance Center. If this feature is enabled, a node cannot be deployed until it meets the check item requirements. For more information, see Configure check items.

    2. DataWorks supports the following deployment scenarios:

      • Standard mode deployment: In a workspace that is in standard mode, you can deploy nodes from the development environment to the production environment.

      • Cross-workspace deployment: In a workspace that is in basic mode, you can deploy nodes to another workspace within the same region and under the same Alibaba Cloud account.

      • Cross-cloud deployment: You can deploy nodes across different Alibaba Cloud accounts, regions, or cloud platforms, such as Alibaba Finance Cloud and Alibaba Gov Cloud.

    Usage notes

    • The deployment time of a node affects when its instances take effect. Changes made during the daily instance generation window (22:00–24:00) take effect two days later. This delay applies regardless of the instance's generation setting. For more information about how instances are generated, see Instance generation.

    • Deployment is subject to permission control. Developers can package pending operations, but only users with the operator role can deploy the packages.

    • Deployment is subject to workflow control. Deployment operations are constrained by role permissions and workflow controls. A deployment is not guaranteed to succeed. Make sure that the node is deployed successfully. If the deployment fails, go to the The deploy task page to check the deployment package status.

    • Only submitted operations can be deployed. Only submitted operations appear on the deployment page in the pending deployment state.

    Deployment process for a standard mode workspace

    1. Go to the Data Studio page.

      Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.

    2. Deploy the node.

      File change operations that pass the checks can be deployed to the production environment on the Deploy > Nodes to Deploy page. The following two deployment methods are available:

      • Deploy a single item: You can click the Deploy button in the Actions column of a single item to deploy it.

      • Batch deployment: You can select multiple items and click Batch Add to Deployment Package at the bottom to deploy them to the production environment in a batch.

      Note

      • Developers can package pending operations, but a user with the operator role must go to the Deployment Packages page to deploy the package.

      • If you want to perform pre-deployment checks, the pending operations must pass the checks before they can be deployed.

    3. View the deployment result.

      After you click deploy, you can view the deployment result on the Deploy > Deployment Packages page.

      Note

      Deployment operations are constrained by role permissions and workflow controls. A deployment is not guaranteed to succeed. Make sure that the node is deployed successfully. If the deployment fails, check the deployment package status on the deployment packages page.

    4. Cancel a deployment.

      If a node does not need to be deployed or the deployment fails, you can perform the following operations:

      • For a node in the pending deployment state, you can click Remove from Deployment Package on the Deploy > Nodes to Deploy page.

      • For a node that failed during batch deployment, you can go to the Deploy > Deployment Packages page, find the failed deployment package, view its details, and click Roll Back to roll back the deployment.

    5. View the version details of a pending file.

      On the Deploy > Nodes to Deploy page, click View in the Actions column of an item to go to the Diff page. On this page, you can compare the pending file version with the version in the production environment to view code or schedule settings differences between versions. You can switch between different versions for comparison.

      For more information about the parameters on the Diff page, see Version details.

    FAQ

    What do I do if the error "Node XXX is already in deployment package XXX and cannot be submitted or deleted" occurs when I submit a node?

    This error indicates that the node is already included in an unfinished deployment package. Go to the Deploy > Deployment Packages page, find the deployment package that contains the node, and handle it based on its status.

    What do I do if the deployment package is in the pending deployment state?

    Have a user with the operator role deploy the package, or delete the deployment package to remove the conflicting node.

    What do I do if the deployment package is in the deployment failed state?

    Choose to redeploy or click Roll Back to remove the failed node from the deployment package.

    How do I resubmit a node after handling the issue?

    After you remove the node from the deployment package, resubmit the node.