A better overall process would be a dispatcher/performer model.
- Read entire sheet into a datatable
- Use Bulk Add Queue Items to add them to an Orchestrator Queue
- Get transaction (if none found, move to end and stop)
- Process the transaction, inside a try/catch. If no items found, Throw error which skips the rest of the steps.
- Log the result (if you need logging) of this transaction, and set the transaction status to finalize it in the Queue
- Loop back to 1
Here is a screenshot of a performer flow:
The benefit of this type of model is it makes both automations (dispatcher and performer) simpler. And using a Queue makes it simple to deal with what you need - skipping the rest of the steps for one item and moving to the next. It also makes it seamless if, say, your performer faults - when you restart it, it just gets the next transaction from the Queue - you don’t have to worry about figuring out where you left off in your loop.