Rif.: Flush queue does not work

[Jacobson-ni]

---

@aputman wrote:

Says it in 2012.  Not sure about later versions.

---

2017 states that it has standard error in functionality.

[pincpanter]

It really looks like a typo in LV 2012 help.

But the final word may be: don't wire an error into a node that you really need to run.

[Jacobson-ni]

Okay so it looks like in 2012 the documentation was changed to read that the functions would operate on error in (this seems to have been a mistake). The mistake was caught in 2013 and fixed in 2014 to say that it uses standard error in functionality.

So it would appear that 2012 and 2013 have incorrect documentation if I read everything correctly.

[mzema]

---

@Jacobson-ni wrote:

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.

---

Well I think you could be right... Damn...

Is there any other thing that can be problem in this error case that flush is not applied as well? Because I do not have idea why this would not work...

[mzema]

---

@Hooovahh wrote:

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.

---

Oh! I am dummy. It was exactly this case in 2016! What a crazy little thing again! Now I will be alway reading whole help case! Thanks a lot... Phewwww