11-17-2017 03:41 PM - edited 11-17-2017 03:42 PM
Of course you have a glaring race condition on your toplevel.
Oh, my! I would be scratching my head in a few days once the other parts were working and I was trying to use the data! Thank you very, very much!
11-17-2017 03:53 PM
@alexgieg wrote:
I changed my VIs to User Events. And they didn't work either. The behavior was the same. So I began messing around and discovered what the issue was. It turns out that "Generate User Event" (and probably "Send Notification" too, but I haven't tested) doesn't generate the event if its error input receives the error you're trying to generate an event about. End result: unwiring the error input from the icon, and using a Merge Errors afterwards, did the trick.
This was a quite silly bug, but I liked learning about User Events, and I will start using them way more than before. Thanks for your suggestions then! They both provided me new knowledge, and pointed me in the right direction!
Yes of course! I wish I had noticed this earlier. I have gotten in the habit of leaving the "send" node (be it queue, notifier, user event) unwired if it is very critical that the message gets sent, like a shutdown message. Then use merge errors if your input may or may not have been an error. If your error in is always an error (as it was in your case) then merge errors will just take the top-most error, and you probably want to retain the error that caused the error case.