When a nested has_many attribute includes an id that isn't in the association, Mongoid raises DocumentNotFound with params that include the parent's id. It builds that with parent.id instead of the association's primary key.

If the association uses a custom primary_key, the value in the error ends up wrong. This is purely an issue with the error message; nothing functional breaks, but I can see it sending someone looking in the wrong place.