> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/zoho/troubleshooting.md). # Fixing Zoho sync errors When a lead can't sync to Zoho CRM, it shows up in **Integrations → Zoho → Reconciliation**, grouped by error type. This article covers each error category — what it means and how to fix it. If you got here by clicking the **?** icon next to a Reconciliation error, the section below matches your error type. Jump straight to it. > **New to Reconciliation?** Read the [Reconciliation overview](/help-center/integrations/crm/reconciliation.md) first — it explains the tab, the icons, the fix-it drawer, and how retry works. The article below assumes you know that vocabulary. *** ## Authentication errors **What you'll see:** "Connection authentication credentials were incorrect at sync." **What it means:** Mobly's Zoho connection isn't authorized anymore. This usually happens when the user who connected Zoho changed their password, lost CRM access, was deactivated, or had MFA enforced — or when Zoho expired the OAuth token. **Fix it:** 1. Go to **Integrations → Zoho → Connect** 2. Re-authorize the connection through Zoho's OAuth flow, ideally with a user who has admin or developer access and is unlikely to lose access Then click refresh on the Reconciliation error to retry the failed leads. *** ## Connection errors **What you'll see:** "We can auth with the connection, but we cannot interact with the mapped objects as desired." **What it means:** Mobly can sign in, but doesn't have permission to read or write the Zoho modules your mappings expect — usually Leads, Contacts, or a custom module. Zoho's profile-based access can revoke specific module permissions. **Fix it:** 1. In Zoho, check the connecting user's profile under **Setup → Users and Control → Profiles** for create/edit access on Leads, Contacts, and any custom modules you've mapped 2. If permissions changed, re-authorize Mobly under **Integrations → Zoho → Connect** Then retry from Reconciliation. *** ## Qualifier mapping is missing or out of date **What you'll see:** "X needs their mapped connections updated." **What it means:** A Mobly qualifier value can't be sent to Zoho because it isn't mapped to anything on the Zoho side. Common when a new qualifier value is added in Mobly but never mapped, or when the Zoho picklist option it was mapped to was deleted. **Fix it:** 1. Click the **wrench icon** on the error row in Reconciliation — it opens a "Fix Value Mapping" drawer with the affected qualifier ready to edit 2. Map the unmapped value(s) to the right Zoho picklist option 3. Save Or do it manually under **Integrations → Zoho → Qualifiers**: find the qualifier, open its **Action** menu, and review every value's mapping. Then retry from Reconciliation. *** ## Object mapping is missing **What you'll see:** "Mapping is missing for X object." **What it means:** Mobly is trying to push a lead into a Zoho module (Lead, Contact, or a custom module) but you haven't mapped any fields on that module yet. **Fix it:** 1. Go to **Integrations → Zoho → Mapping** 2. Find the module section flagged in the error 3. Click **Set Defaults** to auto-populate Mobly's recommended mappings, or map fields manually 4. Save Then retry from Reconciliation. *** ## Required Zoho field is missing **What you'll see:** "Required field X is missing in the CRM" — or — "Were previously mapped but the field is now missing." **What it means:** A Zoho field your mapping points to doesn't exist anymore. Usually someone deleted or renamed the field on the Zoho side, or it's hidden from the connecting user's layout. **Fix it:** Click the **wrench icon** on the error row to open the "Fix Missing Field Mapping" drawer — pick a different Zoho field to map to, or clear the mapping if you no longer need it. If the field was deleted by mistake, recreate it: in Zoho, **Setup → Customization → Modules and Fields → \[module] → New Custom Field**. Then retry from Reconciliation. *** ## Data is too long for the field **What you'll see:** "Exceeded the X field limit." **What it means:** A value Mobly sent (job title, company name, notes, etc.) is longer than the Zoho field's character limit. Most Zoho single-line text fields default to 255 characters. **Fix it:** Click the **wrench icon** on the error row to open the "Fix Field Length" drawer — pick a different Mobly field to map (one whose values fit), or clear the mapping if you don't need this field synced. If you'd rather keep the mapping as-is, change the field type in Zoho to **Multi-line** or **Large** text: **Setup → Customization → Modules and Fields → \[module] → \[field]**. Then retry from Reconciliation. *** ## Data format conflict **What you'll see:** "Data format conflict with the X." **What it means:** A value Mobly sent doesn't match the format Zoho expects for that field — most common with URL fields, phone numbers, email addresses, and dates. **Common example:** A LinkedIn URL field gets just a username (`jdoe123`) instead of a full URL. Zoho's URL field type rejects it. **Fix it:** Two paths. * **Click the wrench icon** on the error row to open the "Fix Data Format Mapping" drawer — useful when the right answer is to remap to a different Zoho field that accepts the format you're sending. * **Click the Log button** on the affected lead to see the exact value Mobly tried to send. If the data itself is wrong (typo'd URL, malformed phone), correct it on the lead in **My Leads**. Then retry from Reconciliation. *** ## Value isn't valid in Zoho **What you'll see:** "Value sent for X is not valid in the CRM." **What it means:** The value Mobly sent isn't one of the allowed options for that Zoho field. Most common with picklist fields that enforce the option list. **Fix it:** 1. In Zoho, **Setup → Customization → Modules and Fields → \[module] → \[field]** and review the picklist's allowed values 2. Either add the missing option in Zoho, or update Mobly's qualifier mapping so it sends one of the existing options under **Integrations → Zoho → Qualifiers** Then retry from Reconciliation. *** ## Not enough data to sync **What you'll see:** "Not enough data to meet X requirement." **What it means:** A field that's required for the sync (usually email) is missing or hasn't been enriched yet. Zoho requires this to create or update the record. **Fix it:** Depends on enrichment state. **If enrichment is still in progress:** Most leads enrich within minutes. Wait, then click refresh on the Reconciliation error to retry. If the field is populated, the lead clears. **If enrichment finished and the data is still missing:** 1. Open the lead in Mobly (**My Leads**) 2. Manually fill in the required field 3. Retry from Reconciliation If a high percentage of leads are hitting this for the same field, the requirement may be too strict for the data you're capturing. Talk to your CSM about adjusting Mobly's enrichment requirements or making the Zoho field optional. *** ## Legacy integration errors **What you'll see:** "Legacy integration error." **What it means:** The error came from the older (legacy) Zoho integration that Mobly is deprecating. **Fix it:** Move to the new Zoho integration — see [Migrating from the legacy integration](/help-center/integrations/crm/migrating-from-legacy.md). After migrating, click refresh on the Reconciliation error — successful resyncs land in Cleared. *** ## Unexpected errors **What you'll see:** "Unable to sync due to an unexpected error not yet categorized." The category label may show as either **UNHANDLED\_ERROR** or **UNCATEGORIZED** — both mean the same thing for you. **What it means:** Zoho returned an error pattern Mobly hasn't seen before, so it can't suggest a self-serve fix. These errors get grouped here so the Mobly team can categorize them and add specific fixes in future releases. **Fix it:** 1. Click the **Log** button on the affected lead and copy the error response 2. Send it to your CSM with the Lead ID The Mobly engineering team uses these reports to add new error categories with specific fixes — so the next person hitting the same issue gets a self-serve answer. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/zoho/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.