# Fix Pipedrive delivery when it is paused

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

> A refused connection, an ended plan, a lost permission, a deleted mapped field, or five rejected leads pauses Pipedrive. What each means, how to resume.

Pipedrive delivery pauses when Pipedrive returns an error that another attempt cannot fix. The Pipedrive page under **Integrations** in the sidebar then shows the pause at the top, and **Needs attention** under it gives the reason with the fix. Pipedrive 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, re-map, or resume Pipedrive. 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 Pipedrive: it no longer accepts the saved connection.` | Pipedrive refused Embers' saved access: the API token was regenerated, the Embers app was uninstalled or revoked, or the connection went unused for 60 days |
| `Pipedrive says this company's subscription is not active.` | The Pipedrive company's trial ended or its subscription is unpaid |
| `Pipedrive refused a permission Embers needs.` | The connected user can no longer add people or leads |
| `Re-map Pipedrive fields: a field Embers writes was deleted or changed type.` | A Person custom field in your mapping was deleted or retyped in Pipedrive |
| `Pipedrive 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 |
| `Pipedrive delivery retries were exhausted.` | Rate limits or outages lasted through every retry |
| `Pipedrive paused after` an error code, or `after receiving HTTP` and a status | Pipedrive refused the request outright for another reason |

One lead refused for its own values does not pause anything: a value Pipedrive will not take, a lead with no name, or a Pipedrive plan limit such as the leads-plus-deals cap. That delivery fails and Embers sends the next lead. Only five in a row pause Pipedrive, and resuming starts the count from zero.

Pipedrive's rate limits, its daily API budget running out, outages, and fields that changed since Embers last read them are retried: the first attempt plus seven more, from 30 seconds out to about 6.3 days. For changed fields, Embers re-reads them and the next attempt uses the new ones.

## Fix and resume

**Reconnect**

### Check the user and the company

In Pipedrive, confirm the user who connected Embers is still active in the company. If you connected with the Embers app, check it is still installed for that user.

### Connect the same company again

Choose **Reconnect Pipedrive** under **Needs attention**. An app connection goes back through Pipedrive's consent screen; a token connection asks for a new personal API token (Pipedrive, **Settings**, **Personal preferences**, **API**). Connecting clears the pause, and reconnecting the same company keeps your settings, so there is no separate resume.

**Subscription or permission**

### Fix it in Pipedrive

For the subscription message, renew the company's Pipedrive plan. For the permission message, a Pipedrive admin gives the connected user rights to add and edit people and leads, or you reconnect as a user who has them.

### Choose Resume

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

**Fields**

### Re-map the field

Choose **Re-map Pipedrive fields**. The mapping marks the field that is gone as **Missing in Pipedrive**: map that Embers field to another compatible Person field, recreate the field in Pipedrive and pick it, or leave it unsent. Saving a valid mapping clears this pause.

### Send a test

Choose **Send test**. A test re-reads your Person fields and writes nothing, and it fails again if a mapped field is still missing.

**Rejected leads**

### Read the last error

The reason names the last error, such as `bad_request` or `feature_capping_leads_limit`. The failed rows on the **Activity** card say why each lead was refused. A plan limit means the company is over its leads-plus-deals cap.

### Fix the cause, then resume

Free up room under the plan limit or turn off **Create a lead**, or fix the field Pipedrive refuses, then choose **Resume**.

## The 60-day connection limit

Pipedrive ends an app connection after 60 days without use. You do nothing about it: once a day Embers renews every app connection that has been quiet for 30 days, including paused and switched-off ones. If Pipedrive refuses the renewal, Pipedrive pauses with "Reconnect Pipedrive". If Pipedrive is down, Embers tries again the next day. A personal API token has no such limit.

## Recover the leads you missed

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

## Troubleshooting

- **The pause returns right after reconnecting.** The user you connected cannot add people or leads, or you connected a different company. Check the user's permissions in Pipedrive.
- **Settings say Pipedrive is limiting requests.** That is Pipedrive's rate limit or daily budget, shared with your other Pipedrive tools, not a broken connection. Try later; deliveries keep retrying.
- **Resume is missing.** Pipedrive 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. Salesforce follows the same pattern: see [Salesforce delivery is paused](/help/troubleshooting/salesforce-delivery-paused/).

## Related

- [Create Pipedrive people and leads from qualified leads](/help/integrations/pipedrive/): Connect the company and map what it receives.

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

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

## Frequently asked questions

**Do I need to reconnect Pipedrive every 60 days?**

No. Pipedrive ends an app connection that goes unused for 60 days, so Embers renews every app connection that has been quiet for 30 days, paused and switched-off ones included. An API token does not expire until you regenerate it in Pipedrive.

**Does running out of Pipedrive's daily API budget pause Pipedrive?**

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

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

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

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

No. Reconnecting the same Pipedrive company keeps your field mapping, lead settings, events, and delivery rules, and clears the pause. Connecting a different company resets the mapping and the lead label.
