I found an interesting bug. Not sure if this is the intended behavior or not. If I unintentionally leave a break point set in the sequence file and sequence editor is executing the sequence file, the sequence editor will just "hang" indefinitely. The RQM side does not why it is just hanging up. RQM could wait indefinitely (days, weeks, months, etc.) For example, we may have a remote PXI chassis somewhere and someone will have to "remote" into the PXI chassis in order to find out why it was it was hung up. A suggestion for improvement: Have the TestStand Execution Adapter ignore the break points or at least disable the break points temporarily until the sequence file has been executed.