All Products
Search

This Product

    DataWorks:Manually triggered nodes

    Document Center

    DataWorks:Manually triggered nodes

    Last Updated:Aug 24, 2026

    If a node does not require periodic scheduling but must run in the production environment, create a manually triggered node. This topic describes how to create a manually triggered node and publish it to the production environment.

    Usage notes

    • If a task does not need to be published to the production environment or operate the production engine, you can create and run it in your personal directory.

    • Manually triggered nodes support only on-demand execution and do not support automatic scheduling.

    • You can create manually triggered nodes only for the following node types: Offline synchronization, MaxCompute SQL, MaxCompute Script, PyODPS 2, MaxCompute MR, Hologres SQL, Python node, and Shell node.

    Create and publish a manually triggered node

    1. Go to the Workspaces page in the DataWorks console. In the top navigation bar, select a desired region. Find the desired workspace and choose Shortcuts > Data Studio in the Actions column.

    2. In the left-side navigation pane, find the image icon. To the right of Manually Triggered Task, click image > New Node and select the type of manually triggered node to create. For more information about the supported node types, see Usage notes.

    3. Enter a name for the manually triggered node and press Enter to open the node editor.

    4. After you write the code, click Run Configuration in the left-side pane. As prompted, configure the Compute Resource and Resource Group for the task. If script parameters are configured, you must also assign values to the Script Parameters.

      Note

      The Select a data source option above the code editor provides metadata auto-completion as you write code.

    5. Click Run at the top of the file to run the current task and view the results.

    6. After the node runs, configure the scheduling properties for the node. Then, click Publish to publish the node to the production environment.

      Follow the on-screen instructions to complete the publishing process.

    Run a manually triggered node in production

    1. After the node is published, click Go to operation and maintenance to go to Operation Center.

      Note

      You can also go to the DataWorks workspace list page. In the top navigation bar, select the target region. Find your workspace and click Shortcuts > Operation and Maintenance Center in the Operation column. In the left-side navigation pane of Operation Center, find Manually Triggered Task O&M.

    2. Run the manually triggered node.

      On the Manually Triggered Node O&M > Manually Triggered Nodes page, find the target node in the list and click Run in the Actions column.

    Other operations

    Clone a manually triggered node

    You can clone an existing manually triggered node to quickly create a new one. The cloned content includes the node's Scheduling Settings information (Scheduling Parameters and Scheduling Policy).

    1. In the Manually Triggered Task section in the left-side navigation pane, right-click the node to clone and select Cloning.

    2. In the dialog box, modify the Name and Path as needed or keep the default values. Then, click Confirm to start cloning.

    3. After the cloning is complete, the new node appears in the Manually Triggered Task section.

    Version management

    Version management allows you to revert a manually triggered node to a specified historical version. You can also view and compare versions to identify differences.

    1. In the Manually Triggered Task section on the left, double-click the target node to open the node editor.

    2. On the right side of the node editor, click Version. On the Version panel, view and manage the Developer Record and Publish Record information.

      • View a version:

        1. On the Developer Record or Publish Record tab, find the version to view.

        2. Click View in the Operation column to view the code and Scheduling Settings of the node.

          Note

          The Scheduling Settings supports Code Editor and Visualization modes. Switch between modes in the upper-right corner of the Scheduling Settings tab.

      • Compare versions:

        On the Developer Record or Publish Record tab, compare different versions of the node. The following example uses the Developer Record tab.

        • Compare within the same environment: On the Developer Record tab, select two versions and click Select Comparison to compare the code and scheduling configuration.

        • Compare across environments:

          1. On the Developer Record tab, find a version of the node.

          2. Click Compare in the Operation column. On the details page, select a version from the Publish Record or Build Records tab to compare.

      • Restore to a version:

        You can revert a node only from the Developer Record tab. Find the target version on the Developer Record tab and click Restore in the Operation column. This reverts the node's code and Scheduling Settings to the selected version.