A manually triggered node (also called an on-demand node) runs only when you trigger it manually — it does not run on a schedule. Use this node type when you need to publish a one-off or ad-hoc data processing task to the production environment and trigger it as needed from Operation Center.
If a node does not need to be in the production environment, create and run it in a personal directory instead — even if the node needs to access the DPI engine in production.
Supported node types
Manually triggered nodes support the following node types:
-
Batch Synchronization
-
MaxCompute SQL
-
MaxCompute Script
-
PyODPS 2
-
MaxCompute MR
-
Hologres SQL
-
Python Node
-
Shell Node
Create and publish a manually triggered node
-
Go to the Workspaces page in the DataWorks console. In the top navigation bar, select a region. Find your workspace and choose Shortcuts > Data Studio in the Actions column.
-
In the left navigation pane, find the
icon. Click 
> Create Node next to manually triggered nodes and select the node type. For supported types, see Supported node types. -
Enter a name for the node and press
Enterto open the code editor. -
Write the node code, then click Run Configuration on the left. Configure the Computing Resource and Resource Group. If the node uses script parameters, assign values under Script Parameters.
The Select Data Source option above the code editor enables metadata auto-completion.
-
Click Run at the top of the editor to run the node and review the output.
-
After the manually triggered node runs, set the scheduling configuration, then click Publish to publish the node to the production environment. Follow the on-screen instructions to complete the publish.
Run a manually triggered node in the production environment
-
After publishing, click Go To Operation Center to open the node in Operation Center.
Alternatively, go to the DataWorks Workspaces page, switch to the target region, find your workspace, and click Quick Access > Operation Center in the Actions column. Then find manually triggered node O&M in the left navigation pane.
-
Run the manually triggered node.
Clone a node
Cloning a node creates a copy that includes the full Scheduling Configuration — including Scheduling Parameters and Scheduling Policies.
-
In the manually triggered node section in the left navigation pane, right-click the node and select Clone.
-
In the dialog, modify the Name and Path or keep the defaults, then click Confirm. The cloned node appears in the manually triggered node section.
Manage node versions
Use version management to view, compare, and revert node versions.
Open version history
In the manually triggered node section, double-click the node name to open the code editor. On the right side, click Versions to open the Versions page, which contains two tabs: Developer Records and Publish Records.
View a version
-
On the Developer Records or Publish Records tab, find the version to view.
-
Click View in the Actions column to see the node's code content and Scheduling Configuration.
Switch between Code Editor and Visualization mode for the Scheduling Configuration using the toggle in the upper-right corner of the tab.
Compare versions
-
Within the same environment: On the Developer Records tab, select two versions and click Compare Selected to compare their code and scheduling configurations.
-
Across environments: On the Developer Records tab, click Compare in the Actions column. On the product page, select a version from Publish Records or Build Records to compare.
Revert a version
On the Developer Records tab, find the target version and click Revert in the Actions column. This reverts both the node code and its Scheduling Configuration.