> 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/marketing-automation/marketo/troubleshooting.md). # Fixing Marketo sync errors When a lead can't sync to Marketo, it shows up in **Integrations → Marketo → 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/marketing-automation/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 Marketo connection isn't authorized anymore. This usually happens when the API user's password changed, the API role's permissions changed, the launchpoint service was disabled, or Marketo expired the OAuth token. **Fix it:** 1. Go to **Integrations → Marketo → Connect** 2. Re-authorize the connection, ideally with a Marketo admin who can confirm the LaunchPoint service is active and the API user role has the right permissions 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 Marketo objects your mappings expect. Usually the API role has lost an Access permission to Lead Database, Activity, or a custom object. **Fix it:** 1. In Marketo, check **Admin → Users & Roles → Roles** for the API role used by Mobly's connection. Confirm Lead Database read/write and any custom object permissions 2. If permissions changed, re-authorize Mobly under **Integrations → Marketo → Connect** Then retry from Reconciliation. *** ## Rate limit errors during sync **What you'll see:** Marketo rate-limit errors in your Marketo error log tied to Mobly's API user — typically during a large initial sync or a re-sync after re-mapping fields. Your IT team may flag it as "Mobly is throwing API errors." **What it means:** Marketo enforces per-account API rate limits (daily request caps and per-second throughput). When Mobly's sync hits the limit, Marketo returns a rate-limit response. **This isn't a failure** — Mobly automatically queues a retry with a delay and the lead syncs on the next attempt. The error you see in your Marketo log is the rate-limit response Mobly handled gracefully on its side. **Fix it:** Usually nothing. Wait a few minutes for the retry cycle to clear. **No leads are lost** — the queue holds them until rate-limit headroom returns. When to actually escalate: * If you're seeing the errors continuously across hours (not just during a sync burst), Marketo's account-level limits may genuinely be exhausted by other tools in your environment. Talk to your CSM. * If a specific lead is still missing in Marketo more than a few hours after capture and you can't find it in Reconciliation either, contact support with the Lead ID — that's a different issue worth diagnosing. This category doesn't appear as its own row in Reconciliation. It surfaces only in Marketo's own logs because Mobly handles the retry transparently before it would count as a sync failure. *** ## 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 Marketo because it isn't mapped to anything on the Marketo side. Common when a new qualifier value is added in Mobly but never mapped, or when the Marketo field 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 Marketo field value 3. Save Or do it manually under **Integrations → Marketo → 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 Marketo object (Lead or a custom object) but you haven't mapped any fields on that object yet. **Fix it:** 1. Go to **Integrations → Marketo → Mapping** 2. Find the object 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 Marketo 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 Marketo field your mapping points to doesn't exist anymore. Usually someone deleted or renamed the field on the Marketo side. **Fix it:** Click the **wrench icon** on the error row to open the "Fix Missing Field Mapping" drawer — pick a different Marketo field to map to, or clear the mapping if you no longer need it. If the field was deleted by mistake, recreate it: in Marketo, **Admin → Field Management → 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 Marketo field's character limit. Marketo string 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, raise the limit or change the field type in Marketo: **Admin → Field Management → \[field] → Field Properties**. 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 Marketo 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. Marketo'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 Marketo 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 Marketo **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 Marketo field. Most common with select fields where Marketo enforces the option list. **Fix it:** 1. In Marketo, **Admin → Field Management → \[field]** and review the field's allowed values 2. Either add the missing option in Marketo, or update Mobly's qualifier mapping so it sends one of the existing options under **Integrations → Marketo → 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. Marketo requires this to create or update the lead. **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 Marketo field optional. *** ## Legacy integration errors **What you'll see:** "Legacy integration error." **What it means:** The error came from the older (legacy) Marketo integration that Mobly is deprecating. **Fix it:** Move to the new Marketo integration — see [Migrating from the legacy integration](/help-center/integrations/marketing-automation/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:** Marketo 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/marketing-automation/marketo/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.