# Fix Emelia delivery when it is paused URL: https://useembers.com/help/troubleshooting/emelia-delivery-paused/ Category: Troubleshooting Plan: Solo and above Updated: 2026-10-01 Last verified: 2026-10-01 > A rejected key, a deleted campaign or list, a campaign with no contact list, or exhausted retries pauses Emelia delivery. How to fix each and resume. Emelia delivery pauses when Emelia answers with something another attempt cannot fix. The reason shows on the Emelia page under **Integrations** in the sidebar (`/integrations/emelia`), either on one configuration's row or on the **Connection** card, depending on what broke. > **Warning: Solo and above, administrators only** > > The Integrations screen requires Solo or above, and only an account administrator can reconnect or resume Emelia. ## The four pause reasons | Reason | Where it shows | What pauses | | --- | --- | --- | | `Emelia API key was rejected. Generate a new key in Emelia and reconnect.` | **Connection** card | Every configuration | | `The campaign has no contact list attached. Attach one in Emelia, then resume.` | The configuration's row | That configuration only | | `Campaign or list no longer exists in Emelia.` | The configuration's row | That configuration only | | `Emelia delivery retries were exhausted.` | **Connection** card | Every configuration | **A rejected key** means Emelia answered 401 or 403, usually because the key was deleted or regenerated in Emelia. Emelia keys have no scopes, so there is nothing to adjust on the key itself. **No contact list** is specific to Emelia. Contacts live in lists, and a campaign enrolls the lists attached to it, so Embers adds each lead to the first list the campaign uses. A campaign with no list attached leaves nowhere to add one. Read more in [campaigns and contact lists](/help/integrations/emelia/#campaigns-and-contact-lists). **A missing target** means the campaign or list the configuration sends to was deleted in Emelia. Your other configurations keep sending. **Exhausted retries** means rate limits, timeouts, or Emelia outages lasted through the first attempt plus seven more, from 30 seconds out to about 6.3 days. Embers stays under 120 requests a minute per connection. Check Emelia before you resume. A campaign that is draft or paused never pauses anything: a contact added to its list waits there until the campaign runs, and the row shows a warning. ## Fix and resume ### Fix the cause Attach a contact list to the campaign in Emelia, or choose **Edit** on the configuration and pick a campaign or list that exists. For a rejected key, copy a new one from Emelia under **Settings**, then **Integrations**, then **API**. The connected card has no key field, so choose **Disconnect**, paste the new key on the **Setup** card, and choose **Save API key**. The disconnect confirmation warns that configurations go with the connection, so note each one's agents and target first. ### Test the target From the configuration's **...** menu. For a list, **Send a test lead** adds one sample lead named "Embers Test" after you confirm. For a campaign, **Check readiness** checks the key and the campaign without adding anyone. ### Choose Resume From the configuration's **...** menu for a campaign or list problem, or on the **Connection** card for exhausted retries. Leads that were waiting are sent. ### Retry what failed The **Delivery status** list on the **Delivery** card shows failed, blocked, and skipped pushes from the last 30 days. Choose **Retry** on a failed or blocked row, or **Send anyway** on a skipped one. Emelia updates a person already in the list rather than adding them twice. ## Leads that are skipped, not paused Emelia finds a person by public LinkedIn URL or by email. A lead with neither is skipped with `no public LinkedIn URL or email for this lead`. Embers never runs a paid email lookup for Emelia, because a lead with a public URL is already addressable. Leads a [delivery rule](/help/integrations/delivery-rules/) holds back are skipped too, with the rule in the reason. Neither kind of skip pauses anything, and a single lead Emelia refuses is marked failed on its own row while the rest keep flowing. ## Troubleshooting - **Leads reach the list but no sequence starts.** The target is a list that no running campaign uses. Attach it to a running Emelia campaign; contacts added to it are enrolled automatically. - **The no-list pause returns right after resuming.** The list was attached to a different campaign. Check the campaign the configuration names. - **Nothing arrives and nothing is paused.** Read the skipped rows first, then check that the configuration is switched on. - **Resume is missing.** Nothing is paused at that level, or you are not an account administrator. 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 Emelia](/help/integrations/emelia/): Connect the workspace and add configurations. - [Control which leads reach each destination](/help/integrations/delivery-rules/): Why a lead was skipped rather than sent. - [Fix HeyReach delivery when it is paused](/help/troubleshooting/heyreach-delivery-paused/): The same pause rules for LinkedIn-only sequences. ## Frequently asked questions **Why does Emelia need a contact list on the campaign?** Emelia keeps contacts in lists and campaigns enroll the lists attached to them. Embers adds each lead to the first list the campaign uses, so a campaign with no list has nowhere to put one. **Does a paused or draft Emelia campaign pause delivery?** No. A contact added to a campaign's list waits there until the campaign runs. The configuration shows a warning, never a pause. **Do I lose my configurations when Emelia pauses?** No. A pause keeps each configuration's agents, target, and delivery rules. Fix the cause and choose Resume.