> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Salesforce

> Contacts that stop syncing, mapped fields that arrive blank, records Salesforce rejects, and fields missing from the Field Mapper.

> [!NOTE]
>
> **A successful export doesn't always mean every field landed.** Blinq can show an export as successful when Salesforce rejected the record, or when Blinq left out a field the connected user can't edit. Check the record in Salesforce, not just the export status in Blinq.

Most problems below come from a setting in Salesforce rather than in Blinq. None of them lose data: contact details and lead form answers stay in Blinq, and reach Salesforce when you [re-export](#after-you-fix-it-re-export) the contacts.

## Nothing is reaching Salesforce

| Symptom | Cause and fix |
| - | - |
| New contacts stopped arriving, but Salesforce shows as connected in Blinq | The connection has expired. The **Integrations** page keeps showing Salesforce as connected, and exports stop without a warning. Open **Settings → Integrations → Salesforce** and go to the **Field Mapper**. If it says "We couldn't refresh your Salesforce connection. Reconnect to load your field mappings.", select **Reconnect** and sign in to Salesforce. Your field mappings and settings are kept. Then re-export the contacts captured while the connection was down. |
| Some contacts never reach Salesforce | They're personal contacts. Contacts captured with no card, or on a personal card, are saved as personal and never export. Share them with your workspace from the contact's **Share** menu, then export them. |

> [!WARNING]
>
> **Use Reconnect, not Disconnect.** Disconnecting keeps your Salesforce settings but deletes your field mappings, so you'd have to set them up again.

A connection can expire when:

* it hasn't been used for 30 days;
* the Salesforce user who connected it is deactivated;
* that user's access to the Blinq app is revoked in Salesforce;
* the same Salesforce user connects Blinq more than five times, for example across a sandbox and production. Salesforce keeps five connections per user for each app and drops the oldest.

## A mapped field is blank in Salesforce

These cases leave one field empty while the rest of the record syncs.

| Symptom | Cause and fix |
| - | - |
| A field is blank on some records but not others | The field only exists on one Salesforce object. When you export as **Contacts**, a contact with no email address goes to Salesforce as a Lead, and so does a contact whose Account Blinq can't create. Fields that only exist on Contact are left out of those Leads. The Field Mapper marks these fields **Contacts only** or **Leads only**. If you need the value on both, create the field on both objects in Salesforce and map it. |
| A field is blank on every record | The Salesforce user who connected Blinq can't edit that field. Before each export, Blinq checks which fields that user can edit and leaves the others out. Give the connected user's profile edit access to the field (field-level security), then re-export. |
| A lead form answer is blank, but other answers sync | The mapping may point at a different field with the same name. Blinq doesn't require custom field names to be unique, so two fields called, say, "Region" can both appear in the Field Mapper. This happens when someone creates a new field instead of reusing one, or deletes a field and recreates it. Map the field your lead form actually uses. |
| City and State are blank even though the lead form asked for them | The mapping uses the enriched **Company City** and **Company State** fields rather than your lead form's City and State questions. Map the lead form questions instead. |
| Lead Source shows "Blinq App" | Nothing mapped to Lead Source had a value, so Blinq filled in its default. Map a Blinq field to Lead Source and its value is used instead. If Lead Source is a restricted picklist, the value must be one it allows (see below). |

> [!TIP]
>
> Renaming a lead form field, or changing its answer options, doesn't break its mapping. Deleting a field and creating a new one with the same name does: the new field needs mapping again. Reuse existing fields where you can.

## Salesforce rejected the whole record

In these cases Salesforce rejects the entire record, so nothing on it is created or updated. Blinq still shows the export as successful.

| Symptom | Cause and fix |
| - | - |
| A record is missing or stale after a contact answered a dropdown question | The mapped Salesforce field is a restricted picklist, and the answer isn't one of its values. The value has to match exactly, capitals included. See [Fixing restricted picklists](#fixing-restricted-picklists). |
| A record with a State is missing | Your org uses State and Country/Territory Picklists, and State is mapped without Country. Map **Company Country Code** as well as **Company State Code**, then re-export. |
| A contact already exists in Salesforce, and Blinq's record isn't created | A Salesforce duplicate rule blocked it. Rules set to **Allow** with an alert still block records created through the API, so they block Blinq too. If the email address is already on a Salesforce Contact that Blinq doesn't manage, Blinq leaves that Contact unchanged and flags the contact as a duplicate. |
| Records fail for other reasons | Check your validation rules and required fields in Salesforce. For example, a rule that requires every Contact to have an Account blocks Contacts Blinq can't match to one. |

### Fixing restricted picklists

Every option on your Blinq dropdown needs a matching value in the Salesforce picklist it's mapped to. Otherwise the next answer that isn't on the list won't sync either. This includes standard fields such as Lead Source.

Your Salesforce admin can fix it in one of two ways:

* **Add the missing values.** In Salesforce, go to **Setup → Object Manager → Lead** (or **Contact**) → **Fields & Relationships**, open the field, and under **Values** select **New**. See Salesforce's guide to [managing picklist values](https://trailhead.salesforce.com/content/learn/modules/picklist_admin/picklist_admin_manage).
* **Make the field unrestricted.** Edit the field and untick **Restrict picklist to the values defined in the value set**, so it accepts any value. See "Restricted Picklists" in Salesforce's [picklist guide](https://trailhead.salesforce.com/content/learn/modules/picklist_admin/picklist_admin_start).

Then re-export the affected contacts.

## A field doesn't appear in the Field Mapper

* **Reload the page.** The Field Mapper loads your fields from Salesforce each time it opens, so a field you've just created appears after a reload.
* **Check field access.** The Salesforce user who connected Blinq needs read and edit access to the field on their profile.
* **Check the connection.** If the Field Mapper shows "We couldn't refresh your Salesforce connection", select **Reconnect**.

## After you fix it: re-export

Re-export the affected contacts from **Contacts → All company contacts**. Blinq updates the records it already manages in Salesforce, using your current field mappings. A matching record that another source manages is left unchanged.

## What to send support

If none of these explain it, email [support@blinq.me](mailto:support@blinq.me) with your workspace name, your Salesforce org URL, the affected email addresses, and roughly when the contacts were captured. A screenshot of the Field Mapper rows involved helps too.

***

### Need help?

For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.