Please listen to @Jon_Smith, REFramework is not suitable for use with Persistence (ie wait for action and resume).
You should have something like this architecture:
- Dispatcher: looping (could be REFramework) automation that picks up the items to be processed, puts them somewhere, and then creates a queue item
- Performer: top down automation that picks up the queue item, creates the Action and then waits
-
- This performer would be on a queue trigger that allows for creation of multiple jobs, and the result is you have multiple jobs - one job for each queue item - suspended while waiting for the Actions to be completed
-
- Once the Action is completed this performer should do the rest of your process, including marking the queue item success/fail etc.
Again, the performer needs to be top down and just process ONE item, not a looping automation that processes multiple items.