Probes (and some other aspects) not working

[JohnGilb]

I'm experiencing an intermittent and annoying issue.

For some reason, in some (not all) of my VIs, the debugging probes list "Not Executed." I am certain that the VI itself is running, since in particular my drive code is having this problem and the robot is still mobile.

In addition, some of these VI's have the task of updating some global variables. If the VI goes from a working state into this "Not Executed" state, it appears to stop updating the global variable, and code that reads from that variable finds stale (unchanging) values.

In some cases, this problem only applies to _some_ of the code in a VI. In my drive code, I have two main loops. One loop reads from globals and sets motor outputs, and the other loop reads from gyros/encoders and publishes that to a local variable. Everything in the drive loop shows "Not Executed", but in my sensor loop one of my encoders has a reliable probe, even though all the other encoders/gyros show "Not Executed."

The best reference I found online was a list of things that were fixed in LV 2011:
ID, Legacy ID, Fixed Issue
255014, —, Probes are listed as Not Executed intermittently on Real-Time target

This is especially painful, since one of the things I like about LabVIEW is the debugging =[

Any idea what this is?