Fork behaviour question

[Pokraka, Michael]

Greetings,
I've noticed the following annoying behaviour:
 
The workflow has a fork: 2 parallel & 1 necessary branch.
In the standard scenario, one branch completes, which causes the other to
cancel and life goes on.
 
However: If branch one has an error and branch two completes, nothing
further will happen until a manual restart. Its this the standard behaviour
as it's probably undesirable in a few (most?) scenarios I can think of
offhand - we don't care about errors as long as the necessary branches are
fulfilled.
 
Effectively this means I have to model redundant 'delete the other branch'
steps within forks to make sure things get done.
 
Is this by design or a bug?
 
Cheers
Michael
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.
 
 =============================================================================