Dec 22nd, 2010, 03:16 AM
<stop /> applies only to externalized flow, not to surrounding job
using a <stop /> tag from within an externalized flow/job stops the flow/job execution, but not the surrounding job. So the flow/job stops, but the surrounding job keeps running, moving on to the step following the externalized flow/job.
This behavior makes sense, but is it the expected behavior? Wouldn't stopping the whole execution (i.e. surrounding job execution) make more sense?
Dec 29th, 2010, 02:49 AM
Thanks, Arnaud. I don't think that was intentional. Can you raise a JIRA?
Mar 13th, 2011, 12:07 PM