[TAV-694] t2: Conditionals fire even on errors Created: 2007-12-17 Updated: 2013-12-11 Resolved: 2008-03-13
|Reporter:||Stian Soiland-Reyes||Assignee:||Tom Oinn|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
The Conditional Branching example does not work, because both constants fire, and one of them is picked by semi-random as the result.
The reason is that the conditional fireing still fires even on an error. A dummy workflow with a string constants "Coordinated from" a beanshell script that does Thread.sleep(5000), shows that coordination works in principle.
However, if the beanshell is changed to throw an Exception, the string constant will still be produced.
|Comment by Tom Oinn [ 2008-03-13 ]|
This is correct behaviour in T2 in terms of existing code. This is because errors at the moment get turned into error tokens and passed out in the data stream, the stream completes so the condition is satisfied. We need to implement the workflow / orchestration level failure mode but this particular behaviour is not a bug.