Fixed #810 - halting of subsequent nodes in ReactiveSequence/Fallback #817
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-added halting of subsequent nodes after a SUCCESS/FAILURE -> RUNNING state change in ReactiveSequence/Fallback by cherry-picking 53e1f15. However, changed the default not to throw exceptions if a subsequent node was RUNNING to keep previous (v3.8.5) behavior and prevent crashes of existing projects which use v3.8 and rely on this capability of ReactiveSequence/Fallback (can be reverted if you want so...)