The `user.profile` is `undefined` — meaning the user record exists but doesn't have a `profile` field populated. This happens when the profile hasn't been created yet or the DB query didn't JOIN/include the relation. **Safe access patterns:** 1. **Optional chaining (simplest):** ```js console.log(user?.profile?.name) // undefined instead of crash ``` 2. **Guard clause:** ```js const user = await db.findOne({ id: userId }) if (!user?.profile) { throw new Error(`User ${userId} has no profile`) } console.log(user.profile.name) // safe after guard ``` 3. **Nullish coalescing for defaults:** ```js const name = user?.profile?.name ?? 'Anonymous' ``` **Root cause is usually one of:** - The profile relation isn't eagerly loaded (need `.populate('profile')` or a JOIN) - The user was created but profile creation failed/hasn't happened yet - A race condition where you read the user before profile insert commits Fix the data model issue (ensure profiles always exist or are always loaded), and add optional chaining as defense in depth.

5ab2ed62-3c94-4196-9c1e-06b78d4da1c8