Standard Error Behavior

Many nodes provide error in and an error out parameters so that the node can respond to and communicate errors that occur while code is running. When you create an application, wire all error inputs and outputs of each node on the diagram so that error information moves through the application in the same way as data values. As your VI runs, each node with error-checking capabilities monitors for error information that is passed to the error input from the previous node. Since each node with error inputs and outputs does the same thing, allowing only valid data or error information to flow through the diagram.

The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way:

error in does not contain an error error in contains an error
13781378
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.
Note When a node responds differently to these values of error in, the differences are documented in the Context Help for the error in input of that node.

If you enable error information to flow through the diagram by wiring all error inputs and outputs, you can also use Error nodes to process information provided by the error, access additional information about the error, and use that information to make run-time decisions based on the error conditions in the application.