> 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/reconciliation.md). # Reconciliation When a lead can't sync to your CRM, Mobly puts it in **Reconciliation** — a per-integration tab that groups failed leads by what went wrong, so you can see exactly which leads need attention and why. This article covers how the tab works. For specific error fixes, jump to your CRM's troubleshooting article (linked at the bottom). ## How to get there **Integrations → \[your CRM] → Reconciliation.** Reconciliation lives inside each CRM integration's configuration page (HubSpot, Salesforce, Pipedrive, Zoho) because every connection has its own sync queue and error history. ## What you'll see A summary donut at the top of the tab tells you what percentage of leads cleared vs. failed across the time you're viewing. Below it, leads are grouped into three states. ### Pre-Sync Leads waiting to sync — either queued behind in-progress jobs or held because your **Sync Mode** is set to **Manual** (in the Connect tab). Click refresh to push them through, or change Sync Mode to **Automatic** if you want them to sync without manual intervention. ### Failed Leads that hit an error. They're grouped by error category — `NO_TAG_MAPPING`, `DATA_VALUE_VALIDATION`, `MISSING_REMOTE_FIELD`, etc. Each group shows: * The error code and a plain-language description * How many leads are affected * Action icons (see below) ### Cleared Leads that synced successfully. Mostly here so you can confirm a fix worked and to see the count vs. failures. ## Filter and find what you need Above the lifecycle tabs: * **Event / Lead toggle** — view errors grouped by Mobly event, or as a flat list of leads * **Event dropdown** — filter to a single event (useful right after a show) * **Search** — find a specific lead by name or email ## What each icon does ### On the error category row | Icon | What it does | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **?** | Opens this article (or the per-CRM troubleshooting article) at the section for this error | | **Wrench** | Opens a fix-it drawer — only shown when the fix is something Mobly can do in-app (e.g., remap a missing field, map an unmapped qualifier value). See "The Fix-It drawer" below. | | **Refresh** | Retries every lead in this error group | | **▼ / ▲** | Expands or collapses the group to show individual leads | ### On the individual lead row | Icon | What it does | | ---------------- | ------------------------------------------------------------------------------------------------------------------- | | **Log** (orange) | Opens the Integration Log panel for that lead — the raw error response from your CRM, plus what Mobly tried to send | ## The Fix-It drawer The wrench icon opens a drawer pre-loaded with the right editor for the error. Drawer titles and what they do: * **Fix Value Mapping** (`NO_TAG_MAPPING`) — map the unmapped qualifier value(s) to a CRM property option * **Fix Missing Field Mapping** (`MISSING_REMOTE_FIELD`) — pick a different CRM field, or clear the mapping * **Fix Data Format Mapping** (`DATA_FORMAT_VALIDATION`) — remap to a CRM field that accepts the format you're sending * **Fix Field Length** (`DATA_TOO_LONG`) — remap to a CRM field with more room, or clear the mapping * **Sync Mode** (frozen leads) — manually sync the lead, or switch the integration's sync mode If you don't see a wrench, the error needs a fix outside Mobly: * **Authentication / Connection errors** → fix in the Connect tab * **Data value isn't valid** → add the option in your CRM, or update the lead in Mobly * **Not enough data** → wait for enrichment, or fill in the missing field on the lead * **Required field missing in CRM** → restore the property in your CRM, or remap inside Mobly * **Unexpected errors** → grab the log and send to your CSM The per-CRM troubleshooting articles spell out each of these. ## How retry works After fixing the underlying issue, retry from one of three places: * **Per-lead refresh** (on an individual log) — retries that one lead * **Per-category refresh** (on the error group row) — retries every lead in that group * **Global retry** (top of Reconciliation) — retries every failed lead for this integration When Mobly retries: * **Fix worked** → lead moves to **Cleared** * **Different problem now** → lead moves to the new error category * **Same problem still** → lead stays where it is ## The Integration Log Click the **Log** button on any lead to open the Integration Log panel. * **Current Issue** tab — the latest error, including: * **Lead Log Response** — the raw error your CRM sent back (often the most useful clue) * **Sent to CRM** — what Mobly tried to send * **Synced** timestamp and **Status** * **Phases** — which step in the sync hit the error (Lead, Company, etc.) * **All Logs** tab — every sync attempt for this lead. Useful for diagnosing intermittent issues or confirming a recent fix actually pushed. ## Error-specific help Each per-CRM troubleshooting article explains what every error means and how to fix it: * [Fixing HubSpot sync errors](/help-center/integrations/crm/hubspot/troubleshooting.md) * [Fixing Salesforce sync errors](/help-center/integrations/crm/salesforce/troubleshooting.md) * [Fixing Pipedrive sync errors](/help-center/integrations/crm/pipedrive/troubleshooting.md) * [Fixing Zoho sync errors](/help-center/integrations/crm/zoho/troubleshooting.md) For Marketing Automation troubleshooting, see [Marketing Automation Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md). --- # 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/reconciliation.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.