The specified lookup is ambiguous: Lookup must return at most one row
Overview
This error occurs when a Lookup operation returns multiple matching records for the specified condition. Lookups are designed to find and act on only one record. When that is not possible, this error is triggered.
Resolution Options
Option 1: Use the "First Match" Option
Enable the "Use first match when multiple results" setting to proceed with the first matching record found.
Use case: You are importing customer data and matching records based on email address. But some customers share the same email (e.g., shared support inboxes). If uniqueness is not critical, enable this option to proceed with the first match — for example, to retrieve a contact ID or status.
Option 2: Use Different Lookup Key Columns
Review your Lookup condition. Instead of relying on a single column, use a more specific one that guarantees a unique match.
Use case: You are using Product Name to look up product data, but multiple products might share the same name (e.g., "T-shirt"). Try using Product SKU or Product ID instead — these are more likely to uniquely identify the record.
Option 3: Use Composite Lookup Keys
Add one or more columns to your existing lookup keys to form a composite key that narrows down to a single row.
Use case: In a multi-branch company, you are looking up employees by Employee ID, but IDs are reused across branches. Combine Employee ID and Branch Code in your Lookup — this makes the match unique within the context of each branch.
Best Practices
- Always aim to construct Lookup conditions that return exactly one matching record.
- Composite keys are particularly useful when dealing with hierarchical data (e.g., same names or IDs across different regions, teams, or business units).
- Avoid using non-unique columns like "Name" or "Status" alone for Lookups.
Useful Links
Related Articles
UPSERT Runs Successfully but Doesn't Insert or Update Data
Overview Sometimes an integration run in Skyvia finishes with Success, but no new data is inserted or updated in the target table. This situation most often occurs when using the UPSERT operation. Why This Happens UPSERT decides whether to Insert or ...Replication: MySQL Error: Row size too large (> 8126)
Overview When performing replication to MySQL you can encounter this error: An error occurred while creating table 'Invoice'. Error: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 ...Zoho CRM: You can only get the first 2000 records error for Notes
Overview When backing up or exporting Notes from Zoho CRM through Skyvia, you may encounter the following error: You can only get the first 2000 records without using page_token param. Why This Happens The Zoho CRM API imposes the following ...A Quick Guide to Importing and Updating Audience Members in Mailchimp
Overview This article explains how to configure an UPSERT operation for the Mailchimp ListMembers object in Skyvia. This is the recommended approach for importing and updating Audience members without creating duplicates. How UPSERT Works for ...HubSpot: hapikey Permission Error
Overview This error is common when working with HubSpot and indicates that the API key (hapikey) used for authentication does not have sufficient permissions to access one or more HubSpot objects. Root Causes The error typically occurs for one of the ...