One option is to make the process go into a sleep/check/sleep/check loop until the check detects the event. But obviously this means your process is sat there doing almost nothing, and if the event takes a long time to occur, then this could be a waste of a valuable license. So another option would be to make the 'part 1' process end, and then start a 'part 2' process sometime later, so that between parts 1 and 2, you can use the machine for something else. But this assumes that you have a valid business reason to delay part 2 until you know when the event will have occurred.
As Shashank says, there is no definitive answer.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------