Use a chain with 3 jobs and a permanent order. E.g. the shell chain example from http://jobscheduler.sourceforge.net/osource_scheduler_howto_shell_chain_en.htm
-Skip state a (the order moves to state b)
-Skip state c
-Stop job sample_shell_b
-Skip state b
Now the order disappears. It is not in the order history and not in the job chain anymore, although it is configured as a permanent order. (After a restart of Job Scheduler the order is reread from the live folder and is back in the chain).