Aborted Job started running in a sequence
Posted: Fri Apr 17, 2009 5:08 am
A job which was in "Aborted" state, started running when initiated through a sequence.
Usually when a job is in "not compiled/Aborted/failed validation" state, the sequence will also abort.
But I wonder how a job in Aborted state started running without the sequence getting aborted.
Can anyone clarify me?
Usually when a job is in "not compiled/Aborted/failed validation" state, the sequence will also abort.
But I wonder how a job in Aborted state started running without the sequence getting aborted.
Can anyone clarify me?