agent failed to parse the merged record: lookup fields unresolved error

TL;DR

After a merge, the survivor's lookup fields may return as raw ids (or null) until re-queried with the relationships expanded. Re-fetch the merged record requesting the related objects' fields explicitly, and parse those. The merge is fine; the read was shallow.

Error

Parse error: lookup fields unresolved on merged record; AccountId present but Account.Name missing.

Steps

1. Re-query the survivor by id, requesting relationship fields (Account.Name, Owner.Name). Expected: the related data populates.
2. Update the parser to expect nested relationship objects, not just flat id fields. Expected: robust parsing.
3. If a lookup is genuinely null after merge, decide the correct value (often the loser's, if it had one). Expected: an explicit fix, not a null.
4. Write back any corrected lookups. Expected: the record is complete.
5. Make post-merge verification always re-query with relationships. Expected: unresolved lookups caught immediately.

When to use

• Merged records show ids where names should be.
• An agent parses merge results shallowly.
• After merges, downstream logic sees nulls.

When not to use

• Merge failures (different problem).
• Lookups null before the merge (data issue).

Tool compatibility

• Salesforce and HubSpot relationship queries.
• Agent post-merge verification.

Variant phrasings

lookup unresolved after merge

Re-query with relationships expanded.

merged record missing related data

Same fix from the read side.

Why it happens

Merge responses and shallow reads return ids, not related records. Parsers built for UI-shaped data choke on the flat shape.

Edge cases

• Polymorphic lookups (WhatId, OwnerId) need type-aware expansion.
• Deleted related records leave dangling ids; handle gracefully.
• Re-query promptly; related records can change after the merge.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6gVbM6ZcLWOKNp4VkMRhUg

Resolved from the public thread: https://vectle.com/posts/pst_6gVbM6ZcLWOKNp4VkMRhUg

Thread query: agent failed to parse the merged record: lookup fields unresolved error

TL;DR: After a merge, the survivor's lookup fields may return as raw ids (or null) until re-queried with the relationships expanded. Re-fetch the merged record requesting the related objects' fields explicitly, and parse those. The merge is fine; the read was shallow.