# Fix HeyReach delivery when it is paused

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

> A stopped, deleted, or senderless campaign pauses one HeyReach configuration; a rejected key pauses them all. How to read the reason and clear it.

HeyReach delivery pauses when HeyReach answers with something another attempt cannot fix. The reason shows in a **Needs attention** card at the top of the HeyReach page under **Integrations** in the sidebar (`/integrations/heyreach`), beside the button that fixes it:

- **A campaign problem** (not running, deleted, no sender) pauses only the [configuration](/help/integrations/heyreach/#add-a-configuration) that sends to it. The item carries its name, as in "Founders Q4 is paused"; other configurations keep sending.
- **A key problem** (rejected key, retries exhausted) pauses the whole connection. The item reads "Delivery to HeyReach is paused".

> **Warning: Solo and above, administrators only**
>
> The Integrations screen requires Solo or above, and only a workspace admin can reconnect or resume HeyReach.

## The five pause reasons

### The API key was rejected

`HeyReach API key was rejected. Generate a new key in HeyReach and reconnect.`

HeyReach keys do not expire, so this is almost always a key that was deleted or deactivated in HeyReach. A retry cannot help, so the pause is immediate. Generate a new key in HeyReach under **Settings**, then **Integrations**, then **HeyReach API**, and replace it as described in [fix and resume](#fix-and-resume).

### The campaign is not running

`Campaign is not running. Start it in HeyReach, then resume.`

Only a campaign that HeyReach shows as running (`IN_PROGRESS`) accepts leads. A draft, scheduled, starting, paused, finished, cancelled, or failed campaign rejects them. A campaign finishing on its own is the usual way a configuration that worked yesterday is paused today. Embers never starts or resumes a HeyReach campaign for you.

### The target no longer exists

`Campaign or list no longer exists in HeyReach.`

Someone deleted the campaign or the lead list. Edit the configuration and choose a new target. Resuming without one does nothing, because there is nowhere to put a lead.

### The campaign has no sender assigned

`The campaign has no sender assigned.`

A campaign needs the configuration's LinkedIn sender assigned to it inside HeyReach. This appears when that sender was removed from the campaign. A sender marked **(needs attention)** in the configuration's sender list has a HeyReach login that needs reconnecting, which is the same problem seen from the other side.

### Retries were exhausted

`HeyReach delivery retries were exhausted.`

Rate limits and HeyReach outages are retried: the first attempt plus seven more, from 30 seconds out to about 6.3 days. Only when every attempt fails does the connection pause. Embers stays under 240 requests a minute against HeyReach's 300 per key, so a rate limit usually means another tool is busy on the same key. Check HeyReach before resuming, or the resume spends the schedule again.

## Fix and resume

### Read where the pause is

An item named after a configuration is a campaign problem; "Delivery to HeyReach is paused" is a key problem. Do not replace the key for a campaign problem: the key is fine, and a new one will not restart the campaign.

### Fix the cause in HeyReach

Start the campaign, assign the sender, or edit the configuration to pick a new target. For a rejected key, choose **Replace API key** on the **Connection** card, paste the new key, and choose **Save new key**. Your configurations and delivery history stay, and the connection resumes.

### Test the target

From the configuration's **...** menu. For a list, **Send test lead** pushes one sample lead named "Embers Test" after you confirm. For a campaign, **Check readiness** checks the key, the campaign status, and the sender, and never pushes a lead.

### Choose Resume

Beside the item in **Needs attention**, or from the configuration's **...** menu. The configuration's agents, target, sender, and rules are unchanged by a pause. Leads that were waiting are sent.

### Retry what failed

The **Activity** card lists 30 days of pushes, each problem with its reason; **Failed** and **Held back** narrow it. Choose **Retry** on a failed or blocked row, or **Send anyway** on a held-back one. A lead that already reached the target is held back as already pushed rather than entering the sequence twice.

## Held back, failed, and paused

| State | What happened |
| --- | --- |
| Held back | A [delivery rule](/help/integrations/delivery-rules/) held the lead back, or it was already pushed. Nothing is wrong |
| Failed | HeyReach refused one lead. Everything else keeps flowing |
| Paused | A configuration, or the whole connection, stopped until you resume |

A malformed profile URL is the usual failed row. A lead Embers knows only by LinkedIn's id link waits while Embers looks up its public profile; one that still has no public LinkedIn address is held back with `profile URL is not a public LinkedIn slug`, because HeyReach cannot open it. Neither pauses anything.

## Troubleshooting

- **The pause returns right after resuming.** The campaign moved out of running again, or the new key belongs to a different HeyReach workspace than the campaign.
- **No senders are selectable.** Every sender's HeyReach login has lapsed. Reconnect one inside HeyReach.
- **Nothing arrives and nothing is paused.** Read the **Held back** rows. A configuration whose agents were all deleted warns `Every agent this configuration used was deleted. Choose agents again.` in **Needs attention** and sends nothing until you edit it and choose agents again.
- **Resume is missing.** Nothing is paused at that level, or you are not a workspace admin.

The same rules apply to [Instantly](/help/troubleshooting/instantly-delivery-paused/), [Smartlead](/help/troubleshooting/smartlead-delivery-paused/), and [Emelia](/help/troubleshooting/emelia-delivery-paused/). To push one lead by hand, [send it from the leads list](/help/leads/send-to-destination/). Send the pause reason and the time to viraj@useembers.com if it does not clear.

## Related

- [Push qualified leads into HeyReach](/help/integrations/heyreach/): Connect the workspace, pick a sender and a target.

- [Control which leads reach each destination](/help/integrations/delivery-rules/): Why a lead was skipped rather than sent.

- [Fix Instantly delivery when it is paused](/help/troubleshooting/instantly-delivery-paused/): The same pause rules for email sequences.

## Frequently asked questions

**Why did HeyReach pause when nothing changed on my side?**

The usual cause is a campaign that finished on its own. Only a running campaign accepts leads, so the configuration that sends to it pauses with "Campaign is not running."

**Does a pause lose my configuration?**

No. A pause keeps the configuration's agents, target, sender, and delivery rules, and so does replacing the API key. Fix the cause and choose Resume.

**Will resuming push a lead into the campaign twice?**

No. Embers pushes a lead once per campaign or list. A lead that already reached the target is skipped as already pushed.
