Fix Emelia delivery when it is paused
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 at the top of the Emelia page under Integrations in the sidebar (/integrations/emelia), in a Needs attention card, beside the button that fixes it. A key problem reads “Delivery to Emelia is paused”; a campaign or list problem is named after the configuration, as in “Founders Q4 is paused”, and that configuration’s row reads Paused.
The four pause reasons
| Reason | Needs attention item | What pauses |
|---|---|---|
Emelia API key was rejected. Generate a new key in Emelia and reconnect. | Delivery to Emelia is paused | Every configuration |
The campaign has no contact list attached. Attach one in Emelia, then resume. | The configuration’s name, then “is paused” | That configuration only |
Campaign or list no longer exists in Emelia. | The configuration’s name, then “is paused” | That configuration only |
Emelia delivery retries were exhausted. | Delivery to Emelia is paused | 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.
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 Needs attention shows a warning with Open Emelia.
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. 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 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
Beside the item in Needs attention, or from the configuration’s … menu. 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. Emelia updates a person already in the list rather than adding them twice.
Leads that are held back, not paused
Emelia finds a person by public LinkedIn URL or by email. A lead with neither is held back 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 holds back show the rule in the reason. Both kinds read Held back on the Activity card, neither 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. Choose Held back on the Activity card 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. Send the pause reason and the time to viraj@useembers.com if it does not clear.
Related
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. Needs attention 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, and so does replacing the API key. Fix the cause and choose Resume.
Was this article helpful?
What went wrong?
Thank you. We read every answer.
Still stuck?
Send us the article you were following and what happened. We answer from the same inbox that writes these pages.