Normally you control this by creating a queued action for step 1 of the process that executes microflow A. Microflow A then ends by creating a queued action for step 2 of the process that executes microflow B, and so forth. Since the queue uses a FIFO approach by default this ensures the steps are started in the right order, since step x+1 is always created after step x has been completed.
The StartTime is only used to store the actual start time of the action (just like the EndTime is only used to store the actual end time of the action).
Thijs, using a scheduled event will added the action to the queue at a certain time. The execution of the action will occur when all previous actions are executed. So you won't have complete control over the execution time.
Okay thanks guys. I used a new scheduledevent entity (associated to a the Mx.microflow entity) to register custom scheduled events. A ScheduledEvent runs now every 10 minutes to see if a custom scheduled event need to be triggerd.
Then, I created a new custom scheduled event record. This record is associated to a microflow that creates the QueuedAction record and calls AppendNewActionToQueue. Now there is control, at least every 10 minutes.