Issue Summary

Basically when updating existing Journey, creates a new rule on automation and disables the previous rule's/versions of that journey. By nature if a rule gets disabled, all the in-fly executions are aborted. 

Steps to Reproduce

1. Create Journey in JSM project
2. This will create an automation rule.
3. Now update the same journey , 
4. You can observe the rule execution in-flight are all aborted due to the update.

Expected Results

If Journey builder rules are modified it shouldn't abort the in-flight rules

Actual Results

Currently when Journey builder rules are modified in-flight rules are all aborted

Workaround

 Currently there is no known workaround for this behavior. A workaround will be added here when available