Hi ! I have the same problem, I follow the thread

It’s the scheduling of the operation block that cannot handle multiple operations from the same order. Say that you have operations 10 and 20 from the same shop order on an operation block and then tries to schedule the operation block. Then maybe the system tries to schedule operation 20 first, but as a result of that operation 10 must be scheduled to start before operation 20 so then that is also rescheduled. So, the dependency between the operations on the same order prevents them from being able to be scheduled from the same operation block.

Thanks a lot Bjorn ! 

Ok I understood the reason for the block; it is a bit limiting for our production because the same resource activity in the same shop order is divided into multiple operations 
in sequence and when I want to schedule in sequence with other operations from others shop orders I cannot sequence correctly. 

For us would be more correct if the operation block allows you to insert multiple operations of the same shop order as long as these are contiguous and the sequence is respected during the scheduling phase.
 

@GOEGTOLONE Have you explored the possibility to sequence operations without using operation blocks? that can be done even for operations within the same order (but even in such case you must be aware of the dependencies between the operations within the same order)

@Björn Hultgren thanks a lot for your help !  In APP10 we don't have this possibility;  the problem is that I cannot sequence this scenario 

because every choice that will be made for shop order 123 (i.e. which operation I choose to insert into the phase block) will produce an overlap in terms of time for orders 456 and 789 will make the workload for the GTO resource overestimated

@GOEGTOLONE  The sequencing functionality is available if you use the Aurena client in Apps 10.