And just as addtional.
If you are running your stuff inside a process model. Terminate will generate a report and you are able to restart once more. Abort will report nothing because process model will be aborted, too.
From p 3-7 of the NI TestStand Reference Manual, "Terminating and Aborting Executions" section:
"When you terminate an execution, all the Cleanup steps, including subsequences the Cleanup steps call, execute normally and disregard the pending termination. If you terminate an execution, or reselect Terminate while a Cleanup step is running and the step monitors for termination, the step terminates prematurely and TestStand proceeds to execute the next Cleanup step. Terminating a Cleanup step terminates only that step and the execution proceeds with the next Cleanup step. When you terminate an execution while the client sequence file is still running, the default process model continues to run, possibly testing the next UUT or generating a report.
Try creating a new sequence file with a message popup in Main and another message popup in Cleanup. Set the message expression to "Main" and "Cleanup" just to make sure there isn't any confusion which is which. Now Run MainSequence and when the execution gets to the "Main" message popup, click Terminate Execution or Ctrl+Shift+F9. Does the "Cleanup" popup occur? Basically, I just want to make sure we have the simplest reproducible case of the behavior you're seeing.
After terminating the sequence the report says that 'Report generation interrupted.'
I am trying to create a sequence in which report should generate after terminating the sequence.
Am I missing something here?
The above thread is over one year old so I recommend creating a brand new thread for higher visibility.
In that thread, could you expand upon what steps your sequence goes through before a typical termination?