If you want it to automatically continue after the error is encountered in 10th row, then you need to plan such that those expected errors is thrown as a business exception. That will allow the next (11th transaction) to continue on without stopping the robot execution. One example for a business exception could be null inputs provided (e.g you did not provide a mathematical expression to calculate).
If you want to manually re-run and continue from the 11th row, then you need to build an external tracker (you can use an excel file) that keeps tracks of completed transactions. Everytime it starts a new process run, it checks the external tracker for status of the transactions, then continues only for the incomplete transactions (11th txn onwards). You can also use an additional column within the original input excel to track completion status of the transaction - as long as there is a flag indicator that persists beyond the process run.