In order for nodes to import, transform, analyze or publish data they must be run. Nodes can be executed individually or you can select multiple nodes in a data flow to run. Multiple sets of nodes can be run simultaneously.
There are several commands in the toolbar which relate to the execution of nodes:
1. Run
Runs all selected nodes.
If any of the selected nodes require input from other nodes which have not yet been run, these other nodes will also be executed.
Status icons indicate the state of each node as follows:
| Node status icon | Description |
|---|---|
|
|
Node has not yet been run. |
|
|
Node is queued to run. |
|
|
Node is running. For composite nodes, this icon is also used to indicate that the node has partially completed its run. For more information on composite nodes, see Composition and inheritance. |
|
|
Node has successfully completed running. |
|
|
Node run has failed. To investigate why the run has failed, click the node to view the error details in the Errors panel on the left of the screen, see Troubleshooting errors. |
|
|
Node run has been rescheduled to run again. This status is caused by advanced looping features, see Creating run dependencies. |
Once a node has been run, the Properties panel will show the node's execution details.
On an individual node, the "Duration" is the total run time. On a composite node, the "Total RunTime" is the sum of the durations of all of the contained nodes (note that some nodes can run in parallel). The "Duration" on a composite node is the end time of the last finished node, minus the start time of the first node. For example, a composite that contains two nodes that each took 1 minute to run would show a "Total Run Time" of 2 minutes. If the first node was executed at 12:00:00, and the second node finished executing at 12:05:00, the composite would show a "Duration" of 5 minutes.
When a node has completed a successful run, the output pins will contain data. Clicking a green input or output pin, or clicking the record count will display the data at that point in the data flow in the data viewer. For more information on using the data viewer, see Inspecting data.
2. Re-Run
Clears the selected nodes and runs them again. The Re-Run button performs the same function as choosing Clear Status and then Run.
3. Stop
Interrupts the current execution. Any queued nodes will no longer be executed, although it may not be possible to stop any nodes which have already started executing.
4. Clear Status
Removes any run information for the selected nodes, and clears the output pins of any data. You might choose to clear the status for a set of selected nodes when you want to run them again with more recent data or property values.
To save system space, you can also delete the run information for one or more data flows from the Directory, see Deleting run data.
Deleting run data
You can save system resources by deleting run data for one or more data flows from the Directory.
The Delete Run Data function clears all visible run data from the selected data flows, including node statuses and output pin data, and also removes any temporary files associated with the run. The Clear Status button available from the Designer toolbar performs a similar function, but the advantage of deleting run data from the Directory is that you can select multiple data flows at once.
- From the Directory, select the data flows for which you want to delete the run data. Press and hold the Ctrl key to select multiple data flows if required.
- Click the menu button in the Details panel and select Delete Run Data.Tip: The Delete Run Data button is only available when you have selected at least one data flow.
The Delete Run Data dialog appears.
- Confirm that you want to delete the run data for the data flows that are listed in the dialog, then click the Delete Run Data button.