The call to _q_postConstructorInit is direct in QNodePrivate::propertyChanged, while it is queued in QNodePrivate::init. This means that the former can be processed before the next submitChangeBatch, where the creation event of the latter is found. Together, this results in a child node creation change arriving at the backend with a reference to a parent that has not yet had a node creation change sent to the backend.