Flush queue does not work

[mzema]

Hello everybody,

I tried to make error check after every case done, so when I found one, it should flush the queue of these following cases and simply goes to error handling case... But... It does not work this way. It just simply ignores the flush and then it goes to the previous cases in queue.

I am clipin just screenshot, since there is not much to look for in another cases, so do not kill me for not putting VI :-D.

Thanks a lot for help in advance

Martin

[pincpanter]

If you wire the error into the Flush Queue node, it will not be executed.

[mzema]

well, decision about the case (error/no error) is before the flush. Look at that case bottom right... The problem is as I said. It goes to different cases, which should be flushed!

[aputman]

---

@pincpanter wrote:

If you wire the error into the Flush Queue node, it will not be executed.

---

Help file says that "This node runs normally even if an error occurred before this node runs."

Are you positive that you are getting an error and not a warning? 

[pincpanter]

---

aputman ha scritto:

---

@pincpanter wrote:

If you wire the error into the Flush Queue node, it will not be executed.

---

Help file says that "This node runs normally even if an error occurred before this node runs."

Are you positive that you are getting an error and not a warning? 

---

LV 2011 help does not say that. I verified this with a little example.

Typically only Close nodes run even when 'error in' is true (and Release Queue does).

[pincpanter]

---

mzema ha scritto:

well, decision about the case (error/no error) is before the flush. Look at that case bottom right... The problem is as I said. It goes to different cases, which should be flushed!

---

I'm saying that Flush Queue will not be run unless you unwire the 'error in' input terminal.

[Hooovahh · Accepted solution]

I did a quick test and the flush function does not operate if an error is passed in.  As stated this type of functionality is generally reserved for closing operations, which you want to still release hardware or resources even on close.

[mzema]

Well, yes. I checked it in highlight mode and then you certainly get error cause of overrun of buffer... And technically what is a difference between warning?

[Jacobson-ni]

There might be another problem that there is an error in to the function enqueueing the "Error" message so I would suspect that the message is never being enqueued.

[aputman]

Says it in 2012.  Not sure about later versions.