Hello, the new module “start scenario” is great, however, if the child scenario is “off” due to an error, all the parent scenario’s also crash. When I was using a webhook all the failed runs came in a queue of incomplete executions, but now I have no queue and my data is lost.
Is there a fix for this?
Did you add an error handler to the “start scenario” module?
If you want it to retry, try using the Break directive.
You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be retried or ignored. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw an error and get turned off.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
The main issue is that if the child scenario is stuck, the cycle of the parent “fails” and the data is lost. Even with error handler, my data would be lost and not be saved as “incomplete excecution”.
In that case, you can use the Make App/API to turn on the child scenario, attempt again, and then resume.
Just to let you know, this module also retries the child scenario (see Advanced Settings), but it isn’t helpful if the child scenario is off in the first place.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
Thank you, but;
If there is an error in the child scenario that requires manual adjustments, the data is stil lost, because the child scenario will never be able to run again automatically.
With the webhook method, I had a queue of data waiting until i fixed the error, this is not the case anymore.
