sequence VI paths are empty until another sequence is loaded, then the relative paths get correctly filled in.

[DLMC]

The specifics

Windows 11 Enterprise

LabVIEW 2022

TestStand 2021

I have four test sequences that use VIs that are all in a common Source Distribution.  I modified the TestStand sequences to use relative addressing, pointing to that Source Distribution.  I have OIs built that reference these test sequences and have my development system set to use the the Run-Time Engine.  All of the sequences work in the their respective OI builds.

Here is the weird bit that makes me uncomfortable.  One of the four test sequences shows VI paths that are empty when I load it into the TestStand editor.  All the VIs show no address given to find them.  Until I load any of the other test sequences, then magically, all the VI paths get filled in.  If I then close the other sequence, that test sequence that had blank paths, reverts to blank paths again.  I never noticed this before because I tended to have multiple test sequences loaded when I worked on them.  The sequences show this even when they are locked.

Why?

I admit, this is more of an annoyance than a crisis because all I need to do is load another sequence and everything comes back.  What makes me worry is will this happen when deployed, at some random time.  I have restarted the TestStand editor and rebooted, and the issue remains.

Has anyone else seen this?

be well,

DLC

[DLMC]

Solved.

The Search Directories for that sequence file did not have the root directory the code executed listed.  The other sequences did, so when they were loaded, that directory got added to the list.

Kind of obvious and kind of subtle.  At least to me.

be well,

DLC