Ignore notifier output in the VI "Wait on Notification" if its data type is the error cluster

[Matthias_H]

I don't know if it's a bug or a feature but I think it is very unuseful.

I often use notifiers to handle my errors. The parallel loops send an error to an error handling loop and there the error will be logged within a file for example.

The following VI thows an error because the notifier message output includes an error and automatic error handling is set to on. In my optinion this output should not be included within the error handling because in this case it is only some kind of data and not a "real" error.

[RavensFan]

Strange.

I don't think this should be considered a new idea.  It should probably be posted in the LabVIEW forum and looked at as being a bug.

Actually, the Wait on Notification does not throw an error.  Put probes on the wires or turn on highlight execution.  Even put an error indicator out at the end of the chain.  Nothing shows an error, but yet at the end, a dialog pops up and says "Error 1 occurred at unidentified locations".  If you wire up something into the source string of the error cluster, then that string will show up as the location in the pop up.

Now a work around to this would be to drop your error cluster into another cluster, then the pop up error does not occur.

I think there is a bug.  My gut feel is the error is actually occurring upstream at the Send Notification, and somehow it is corrupting the memory of the notification.  Even if you take out the Wait on Notification, the pop up error stills occurs.

[AristosQueue (NI)]

This is deliberate. Automatic Error Handling is designed to catch errors no matter where you propagate them until you send them some place to be handled. If you have a loop that sends an error out, and you have some place else that receives that error, it is just as much unhandled as if it had still been on the main error terminals. It can often imply that you have forgotten to wire an output in your error handler VIs.

The question is: Why are you waiting on that notification if you're not planning to do anything with it? If you're just wanting a signal from the other end that it is done, error or no error, wire the error output to the border of a sequence structure to deliberately throw the error away.

[Matthias_H]

"The question is: Why are you waiting on that notification if you're not planning to do anything with it?"

I handle the errors and in special situations I'll quit my application. And the VI to close the notifier throws an error if the notifier includes an error.

[SteenSchmidt]

Don't enable automatic error handling. Ever.

Cheers,

Steen

[JordanG]

Per Aristos Queue's comments below