Table Of Contents

Destroy Stream Endpoint (G Dataflow)

    Last Modified: January 12, 2018

    Destroys the specified endpoint.

    Programming Patterns

    Use the Flush Stream node on the writer endpoint prior to this node to ensure you do not lose any data when destroying a stream.


    endpoint in

    Reference to the endpoint. Obtain this reference by wiring endpoint out from another network stream node, such as Flush Stream or Read Multiple Elements from Stream, to this one.


    error in

    Error conditions that occur before this node runs. Unlike most nodes, this node runs normally even if an error occurs before this node runs.

    Default: no error


    error out

    Error information.

    The node produces this output according to standard error behavior.

    Standard Error Behavior

    Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. 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
    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.

    Free Memory Allocated to a Stream

    To completely destroy a stream and free up the memory allocated to that stream, you must destroy both the reader and writer endpoints.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Not supported

    Web Server: Not supported in VIs that run in a web application

    Recently Viewed Topics