it is perfectly alright to have both dispatcher and performer in RE frame work. we can have the dispatcher work flow in init state first run.
We have to consider some of the scenarios like where it will take huge amount of time to get the data by using dispatcher workflow. in some case like it will take 5 to 6 hours to get the input data from the application so we cannot wait those many hours to gather our input data instead of that we have to go the approach like maintain the dispatcher and performer in two different processes and we can connect both of them by using Queue triggers. in this case whenever we get the transaction from dispatcher queue it will automatically trigger the performer bot.
if the use case you mentioned is not fall under above scenario you could have dispatcher and performer in the same RE framework.
if you have any additional questions please share us in this post so that our forum members will help you. thanks.
Hey,
regardning my experience.
For more complicated processes, I always use two processes: the dispatcher and the performer.
The dispatcher collects the data and passes them to the queue, and the trigger is set on the queue’s element and launch only when there is something to be done.