Both methods I described will return to the next step or next sequence call. After running one of your sub-sequences now, doesn't TestStand return to the next step? Do a simple experiment. Create a sequence called "Pause". In this sequence, put a a pop-up. Place a call to the new sequence after any of your steps. When the sub-sequence is called, you'll get the pop-up and when you click the OK button, you'll return to the next step in your sequence. Now, instead of a just a pop-up, add some code to check the current time and skip the pop-up if it's not the end of the shift. Instead of a pop-up, you could instead, go into a while or for loop that again checks the current time but doesn't exit until it's start of the shift. It all depends on whether you want a person actually there to resume the test or for it to resume automatically. Personally, I would prefer to do the post step callback so that I wouldn't have to add a sequence call after step but that's up to you.