Using order_inserts in our project sometimes results in constraint violations because rows for a given entity are inserted before other rows to which they refer via foreign keys.

We have struggled to reproduce this as a minimal test case. However we have identified the problematic code:

ActionQueue.InsertActionSorter, line 877, checks if each property of the entity under consideration is another entity type. This doesn't work if the property is an @Embedded class. Consequently it's possible to arrange inserts into an incorrect order.