Break the behaviour down into states like in the attached image.
The Success state could send an event to another FSM to trigger some behaviour. This keeps the Touch FSM nice and simple.
The key is to break behaviours down into simple steps and use smaller FSMs that talk to each other.
You can also think of an FSM like a flowchart, where you're breaking behaviours into simple, discrete steps.
Does that make sense?
