Hi Everyone,
is there a way to stop a scenario execution on purpose?
I know the error handling modules (commit, ignore…) but in my case it’s not an error.
The marked “Search Rows” modules has 10 collections and in most cases I only need three (or 4,5,6…). This is the case when I reach the “Update Row” module where I put the “commit” module and that’s when/where I want to end the execution although there is no error.
One option would be to put another module which always leads to an error and then put the commit module, but is there a way to do it without this?
Best,
Richard
Have you tried using a ‘break’ module to achieve this?
1 Like
Thanks for your suggestion. Sadly, the break module is an error-handling module as well. So it’s not going to the break module after a successful operation.
I went on to create an error on purpose 
The marked “Search Rows” modules has 10 collections and in most cases I only need three (or 4,5,6…). This is the case when I reach the “Update Row” module where I put the “commit” module and that’s when/where I want to end the execution although there is no error
When/how do you reach the route when you are finished and have enough bundles? Why don’t you use that same logic at the first router you have after the “Search rows” module to filter out any data that you don’t need anymore. I can’t see your details of the scenario unfortunately, so if that doesn’t work the best would be to add another module which always errors & an ignore handler.
Cheers!
~john
1 Like
@Bjorn.drivn thanks for your suggestions. It would be a little longer to explain but I can’t filter them at that stage. I only know it at the module on the right and that’s where I would need a module to “end scenario execution”.
But yeah I went with the planned error.
1 Like
Hello @Richard_Johannes, Did you find a solution to stop the scenario on purpose ? If you do I would really enjoy to heard your solution because I’m facing the same problem …
Hi @Benjamin_Kratiroff,
I think I’ve used the HTTP Module with a random, non-existent URL which always gives an error. I then used the commit error-handler to stop the scenario 
1 Like
