# Fix Salesforce delivery when it is paused

URL: https://useembers.com/help/troubleshooting/salesforce-delivery-paused/
Category: Troubleshooting
Plan: Solo and above
Updated: 2026-10-26
Last verified: 2026-10-26

> A refused connection, lost API access, a deleted LinkedIn URL field, or five rejected leads in a row pauses Salesforce. What each means and how to resume.

Salesforce delivery pauses when the org returns an error that another attempt cannot fix. The Salesforce page under **Integrations** in the sidebar then shows the pause at the top, and **Needs attention** under it gives the reason with **Resume**. Salesforce sends no email when it pauses.

> **Warning: Solo and above, administrators only**
>
> The Integrations screen requires Solo or above, and only a workspace admin can reconnect or resume Salesforce. See [what each role can do](/help/reports-and-workspaces/team-and-roles/#what-each-role-can-do).

## Read the pause reason

| Reason | What it means |
| --- | --- |
| `Reconnect Salesforce: it no longer accepts the saved connection.` | Salesforce refused Embers' saved access: it was revoked, the app was blocked, or the connection expired |
| `Reconnect Salesforce: the Salesforce user who connected it is deactivated.` | The user Embers writes as was deactivated |
| `Reconnect Salesforce: the Salesforce org is no longer active.` | The org itself is inactive |
| `Salesforce refused API access for this org.` | The org's edition has no API access |
| `Salesforce refused API access for the connected user.` | The connected user lost the "API Enabled" permission |
| `Pick the LinkedIn URL field again` | The field Embers writes the LinkedIn URL to was deleted or can no longer be edited |
| `Salesforce refused a field Embers writes.` | Salesforce rejected a field without any change Embers could see in your schema |
| `Salesforce paused after 5 leads in a row were rejected (last: ...)` | Five leads in a row were refused for their own values, with none delivered between |
| `Salesforce delivery retries were exhausted.` | Limits or outages lasted through every retry |
| `Salesforce paused after` an error code, or `after receiving HTTP` and a status | Salesforce refused the request outright for another reason, such as missing access |

One Lead refused for its own values does not pause anything: a missing required field, a validation rule, an invalid email, a duplicate rule with no usable match, a restricted picklist value, or a trigger or flow that failed. That delivery fails and Embers sends the next lead. Only five in a row pause Salesforce, and resuming starts the count from zero.

The org's daily API limit, outages, record locks, and a field hidden since Embers last read your schema are retried: the first attempt plus seven more, from 30 seconds out to about 6.3 days. For a hidden field, Embers re-reads the fields and sends the next attempt without it.

## Fix and resume

**Reconnect**

### Check the user and the org

In Salesforce, confirm the user is active and that the Embers app is still allowed. If the user was deactivated, connect as a different one. A user who is not a Salesforce admin is refused on the consent screen unless an admin has installed the app under **Setup**, **Connected Apps OAuth Usage**.

### Connect the same org again

Disconnect Salesforce from the **...** menu beside the status, then connect again the way you first did: Production, Sandbox, or My Domain. Connecting clears the pause, and reconnecting the same org keeps your settings, so there is no separate resume.

**API access**

### Restore API access

For the org message, the edition needs API access: Enterprise, Unlimited, Performance, or Developer Edition, or Professional Edition with the API add-on. For the user message, a Salesforce admin gives the connected user the "API Enabled" permission, through their profile or a permission set.

### Choose Resume

**Resume** sits beside the pause under **Needs attention**.

**Fields**

### Fix the field in Salesforce

For **Pick the LinkedIn URL field again**, recreate the field or pick another custom text or URL field the connected user can edit. Picking the field again clears this pause. For **Salesforce refused a field Embers writes**, check the connected user can edit the [Lead fields Embers writes](/help/integrations/salesforce/#what-embers-writes-to-a-new-lead).

### Resume and test

Choose **Resume** if the pause is still shown, then **Send test**. A test re-reads your fields and writes no record, and it fails again if the LinkedIn URL field is still gone.

**Rejected leads**

### Read the last error

The reason names the last error, such as `REQUIRED_FIELD_MISSING` or `FIELD_CUSTOM_VALIDATION_EXCEPTION`. The failed rows on the **Activity** card carry each one. Usually a required custom field, a validation rule, or a flow refuses every Lead Embers sends.

### Relax the rule, then resume

Give the field a default, or let the rule allow Leads from the connected user, then choose **Resume**.

## The 30-day connection limit

Salesforce ends Embers' access after 30 days without use. You do nothing about it: once a day Embers renews every connection that has been quiet for 20 days, including paused and switched-off ones. If Salesforce refuses the renewal, Salesforce pauses with "Reconnect Salesforce". If Salesforce is down, Embers tries again the next day.

## Recover the leads you missed

Leads that qualified while Salesforce was paused were kept as **Blocked**. After you resume, choose **Retry** on a blocked row on the **Activity** card, or [send the leads to Salesforce](/help/leads/send-to-destination/) from the leads list. A lead Embers already linked is skipped as `already synced to Salesforce Lead` and its record ID unless you tick **ignore rules**, which updates that record rather than making another.

## Troubleshooting

- **The pause returns right after reconnecting.** The new user lacks "API Enabled" or Create on Leads, or you connected a different org. Check the user's permissions.
- **Settings say the org has used its API requests for today.** That is the daily API limit, not a broken connection. Try later; deliveries keep retrying.
- **Resume is missing.** Salesforce is not paused, or you are not a workspace admin.

Send the pause reason and the time to viraj@useembers.com if it does not clear. HubSpot follows the same pattern: see [HubSpot delivery is paused](/help/troubleshooting/hubspot-delivery-paused/).

## Related

- [Create Salesforce Leads from qualified leads](/help/integrations/salesforce/): Connect the org and choose what it receives.

- [Send a lead to a destination](/help/leads/send-to-destination/): Push the leads you missed during a pause.

- [Fix HubSpot delivery when it is paused](/help/troubleshooting/hubspot-delivery-paused/): The same pause rules on the HubSpot side.

## Frequently asked questions

**Do I need to reconnect Salesforce every 30 days?**

No. Salesforce ends a connection that goes unused for 30 days, so Embers renews every connection that has been quiet for 20 days, paused and switched-off ones included. You only reconnect if Salesforce refuses that renewal, and then Salesforce pauses with "Reconnect Salesforce".

**Does hitting the org's daily API limit pause Salesforce?**

No. Deliveries retry on the usual schedule, the first attempt plus seven retries over about 6.3 days. Only if every attempt fails does Salesforce pause.

**Will I get an email when Salesforce pauses?**

No. Salesforce pauses send no email. The Salesforce page and its card on the Integrations page show the pause.

**Do I lose my settings if I reconnect?**

No. Reconnecting the same org keeps your LinkedIn URL fields, Lead Source, Task setting, events, and delivery rules, and clears the pause. Connecting a different org resets the LinkedIn URL fields and Lead Source.
