RichM -
There should be no difference in behavior between a sequence in the current file and a sequence in a different file. I suspect that another setting is the cause.
I assume that you are using on-the-fly logging. Currently the on-the-fly database logging will log a parent sequence call step when at least one of its children is logged, even if the parent may not be logged. For example a parent step can pass when a child step fails if the step setting says to not propagate the failure.
The on-the-fly logging does this because at the time of logging the single step, TestStand does not know if the parent will be logged because the filter expression cannot be evaluated for it until the result for the parent is created, and this will not happen until
the after the child is logged.
If you do not use on-the-fly, i.e. "post-UUT logging", the parent step will not be logged because the parent result is logged before the child.
Scott Richardson (NI)
Scott Richardson