Hi dude,
Sometimes it's due to an actual missing VI but lately I have been copying libraries full of classes from one project to another and end up with missing VIs.
So it is not just "sometimes" but "always" the problem of missing VIs.
And it's all your fault when YOU start to move things on harddisc without using the project explorer…
The annoying part is that I just see a square with a question mark where the VI should be. Figuring out what VI is missing is often a real challenge if you are not the author of the code!
Three simple steps:
1. Open the context help.
2. Move the mouse pointer over the missing subVI.
3. Read the text in the context help.
Best regards,
GerdW
using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019