I want a Stop & Commit module that stops the scenario execution immediately and marks its status as a success. Of course, you can already do this by using a module to purposefully trigger an error and then attaching a Commit error handler. However, this clumsy solution may not be evident to many users since their intent isn't to handle an error but to end a successfully executed scenario. A Stop & Commit module would come in handy for scenarios that contain many nested routers, which is something I have found necessary to space out lines of automations so the overall scenario is easier to visualize and work with. An example of such a scenario is when different tags are added to a contact in a CRM, with each tag being used as a filter to run a different line of automation with a unique sequence of modules. Since all of the lines of automation must share the same trigger now in Make, once more than a few tag-filtered lines of modules are added, the scenario becomes a confusing mess without adding a tree of nested routers to space things out. Once a tag-filter is passed, the router tree has fulfilled its purpose, but without a Stop & Commit module, execution continues unnecessarily throughout the remaining router tree checking all the remaining tag-filters. Note: A Stop & Commit module wouldn't be appropriate in the example above if an Iterator module was used because multiple tags may be added to a contact at once, and each tag is meant to trigger a different line of automation. A Stop & Commit module would end execution after the first tag passes its filter, its automations are run, and the Stop & Commit module is reached. Meanwhile, the subsequent tags would not cause their intended lines of automation to execute. In that situation, a Next Iteration module would be needed, which I've suggested in another post.
