Home > Workflows > Workflow Nodes > Run Node
You perform the tasks specified in the workflow by running one or more nodes. To run a node, right-click the node and select Run from the context menu. If a node depends on outputs of one or more parent nodes, the parent node runs automatically only if the outputs required by the running node are missing.
You can run a node in more than one way:
Run runs any tasks that have not already run. For example, if you add a new model to a Build node, Run builds the new model and does not rerun any models that are complete.
Force Run reruns the node. In a model build node, all models are built, even the ones that are complete.
Each node in a workflow has a state that indicates its run status, as described in Node States.
Nodes can't always be run. If any ancestor node is in the Invalid state and its outputs are missing, the child nodes that depend on it cannot run.
When a node is running, the workflow is locked, and none of its nodes can be edited. Existing results may be viewed while the workflow is running. You can also go to a different workflow and edit or run it.
When a workflow is running, an animation in the tool bar (circular arrow loop) shows that the workflow is running.
When a user opens a workflow, the workflow is locked so that other users cannot modify it.
When you open a locked workflow, Locked is displayed in the toolbar and a running indicator if the workflow is running:
If a workflow seems to complete, but is still locked, clicked Locked to unlock the workflow.
You also see the workflow nodes highlighted that are running as you would do if you had submitted it to run (even though it is locked). Once a locked workflow has stopped running, you can refresh the workflow (by clicking the toolbar refresh icon), or you can try to obtain the lock yourself by clicking on the lock.If no one else has the workflow locked, you are given the lock, and the lock icon is removed from the toolbar.You can also cancel a running workflow even if you did not originally lock it.