I have a test application where rendezvous are used to synchronize certain test steps - however, not all units under test run the same test steps depending on the cycle number, so in (for example) cycle 2, the number of threads for the rendezvous is different than cycle 1.
However, when the second cycle comes around, a TestStand exception is thrown saying that "The Rendezvous <RendezvousName> already exists with a different number of threads>" which looks like it could only happen if the rendezvous object from the previous cycle was still somehow considered 'active' or 'existing' by TestStand. This error pops up even when the Rendezvous Lifetime is set to "Same as Sequence" and the Sequence File Option is set to "Unload After Sequence Executes", so I'm not really sure why the error is being thrown.
Does anyone know how I can manually 'destroy' or clear out, or otherwise clean up the rendezvous object so that it doesn't persist (apparently) between cycles?