Thank you very much for your enthusiastic comment.
It's nice to hear people actually think about the solution instead of trying to solve it using trail-and-error. My original idea was to make some "process" button, like it was some machine and the user had just a few tries and/or would be scored based on the number of tries they needed.
But I dropped it, felt like it would make the experimentation and seeing what the outcome would be too tedious. But maybe I should've added some kind of scoring mechanism - the less tries you used, the higher the score.