Rule Component Sequencing
This change was released on July 7th, 2020.--We've made a significant update to the Launch browser runtime to add a new capability. This article will clearly describe the legacy behavior, the new behavior, and some things you should consider as you make the move. Let's dive in!1) Legacy behaviorWhen a rule contains multiple actions, Launch will call those actions in the same order that you have them organized in the interface. In this example, Launch will call Action A, then Action B, then Action C.What Launch does not do is wait for Action A to finish before it calls Action B. If Action A is synchronous, then it doesn't matter much. But if Action A is asynchronous, then Action B probably starts to run while Action A is asynchronously carrying out its task. Over the long-term, we'd expect to see that sometimes Action A finishes before Action B, but sometimes it finishes afterward. The same is true for Action B
