While executing the “repeat” action after a while it show me an error: to found out what it’s happening I have to manually cycle the executions since I reach the one with the error. It could be really good to have the possibility to reach the correct "loop” without manually cycle.
Suggestions
Mode 1 - while a Repeat action faults, show a button that can bring the user to the instance that caused the error.
Mode 2 - in the “Send/save output to” window put an option “Run until error”
maybe I'm misunderstanding your question. What I'm understanding is that you'd like to somehow save the state of a loop iteration when it runs into an error.
If the error isn't a bug in easymorph (the kind that produces a HRESULT: 0x... kind of error), you should be able to catch the faulty data, in one of two ways:
reconfiguration of the easymorph flow: splitting it before the error point, adding a derived table that executes only if the approximate error condition occurs and then saves the data to a file
using the built-in "Capture errors and continue" option and saving loop results to a file instead of returning it as a result table. That way, you should be able to diagnose which page produced the error (the one with missing result data) if you include the page number in the output.
These options certainly aren't as convenient as just having the option to let easymorph run until it hits a roadblock. That would mimick the functionality of the "Breakpoint" action, but treat any error as if it were a break point.
I confirm that your suggested methods are the ones I’m using to manage this situation but in my opinion is not a professional solution, the breakpoint could be more efficient!