# Fix Slack delivery when it is paused URL: https://useembers.com/help/troubleshooting/slack-delivery-paused/ Category: Troubleshooting Plan: Solo and above Updated: 2026-10-17 Last verified: 2026-10-17 > Read the Slack pause reason, fix a revoked token, a missing or archived channel, or a removed bot, then resume and retry the posts you missed. When Slack answers with an error that another attempt cannot fix, Embers stops posting instead of retrying into a dead channel. The Slack page under **Integrations** in the sidebar (`/integrations/slack`) then reads "Posting to Slack is paused" at the top, and **Needs attention** under it shows the reason, such as `Slack paused after not_in_channel.`, with **Resume**. > **Warning: Solo and above, administrators only** > > The Integrations screen requires Solo or above, and only a workspace admin can reconnect or resume Slack. See [what each role can do](/help/reports-and-workspaces/team-and-roles/#what-each-role-can-do). ## What pauses an install Rate limits, timeouts, and Slack server errors are retried: the first attempt plus seven more, from 30 seconds out to about 6.3 days. If every attempt fails, the install pauses with `Slack delivery retries were exhausted.` A terminal error pauses the install on the first occurrence. The reason names the Slack error. When Slack refuses the request with an HTTP error instead, it reads `Slack paused after receiving HTTP` and the status code. A message Slack refuses for its content, such as `invalid_blocks`, `msg_too_long`, or `no_text`, is not a terminal error. That one post fails, with the reason on its row on the **Activity** card, such as "Slack refused how the post was laid out (invalid_blocks)", and Embers keeps posting other leads. Only five of those in a row, with no post landing in between, pause the install, with `Slack paused after 5 messages in a row were rejected` and the last error. A lead that a [delivery rule](/help/integrations/delivery-rules/) stops is listed as **Held back**, not failed, and never pauses anything. If nothing is posting and the status still reads "Posting to" your channel, choose **Held back** on the **Activity** card first. ## Fix the reason **invalid_auth, token_revoked, token_expired, or account_inactive** The stored bot token no longer works. The Embers app was removed from the Slack workspace, a Slack admin revoked it, or the workspace itself was deactivated. Reinstall: open the **...** menu beside the status, choose **Disconnect Slack** and confirm, then choose **Connect Slack workspace**, approve the app in Slack, and pick the channel again. Your event toggles and delivery rules are kept; the channel is not, because disconnecting clears it. **channel_not_found** The channel Embers posted to was deleted or can no longer be seen. On the **Channel** card, choose a channel under **Delivery channel** and select **Save channel**. Saving a channel clears the pause on its own, so there is nothing else to resume. A private channel appears in the list only after the Embers app has been added to it. **not_in_channel** The Embers app was removed from a private channel. Public channels do not need an invite, so this is almost always a private one. Add the Embers app back to the channel in Slack, then choose **Resume**. **is_archived** The channel was archived. Unarchive it in Slack and choose **Resume**, or pick a different channel and save it. Archived channels are left out of the channel list. **ekm_access_denied or team_access_not_granted** Slack Enterprise Key Management, or an Enterprise Grid workspace grant, is blocking the app. A Slack admin has to restore access to the Embers app for that workspace. Then choose **Resume**. **5 messages in a row were rejected** Slack refused five lead cards in a row for their content. Embers builds the card, so there is nothing to change in Slack. Choose **Resume**. Resuming Slack, choosing a channel, switching delivery back on, or reconnecting starts the count from zero, so Slack pauses again only after five more rejected cards in a row. If the install pauses again, email the reason and the time to viraj@useembers.com. ## Resume and retry what you missed ### Fix the cause in Slack Reinstall the app, add it back to the channel, unarchive the channel, or pick a new one. Resuming without fixing the cause pauses the install again on the next delivery. ### Choose Resume **Needs attention** shows **Resume** beside the pause while the install is paused. It keeps your workspace, channel, event toggles, and rules exactly as they were. ### Send a test **Send test**, beside the status at the top of the page, posts a sample card to the channel, built the same way as a real delivery. It is disabled while the install is paused or turned off, or has no channel it can post to. ### Retry the failed rows The **Activity** card lists every post from the last 30 days with its status, the reason in words, and the time; the **Failed** and **Held back** filters narrow it. Choose **Retry** on a failed or blocked row, or **Send anyway** on a held-back one. The newest three failed posts are also under **Needs attention**, each with **Retry**. The buttons appear only while posting is on and not paused. A post that already reached Slack is never posted twice: Embers records the Slack message and skips any delivery that has one. To post a lead that is older than the 30-day history, [send it from the leads list](/help/leads/send-to-destination/). ## Troubleshooting - **The install pauses again right after resuming.** The cause was not fixed, or a different error replaced it. Read the new reason; it may name another Slack error. - **The private channel is missing from the list.** The Embers app has not been added to it. Add the app in Slack, then reload the channel list. - **Resume is missing.** Either the install is not paused (check the status at the top of the page), or you are not a workspace admin. - **Posting works but some leads never arrive.** Delivery rules are holding them back; they are not failing. Choose **Held back** on the **Activity** card to read each reason. If none of that clears it, email the pause reason and the time it happened to viraj@useembers.com. The same pause pattern applies to [HubSpot](/help/troubleshooting/hubspot-delivery-paused/) and [signed webhooks](/help/troubleshooting/webhook-endpoint-paused/). ## Related - [Send qualified leads to Slack](/help/integrations/slack/): The install, the channel, and the event toggles. - [Control which leads reach each destination](/help/integrations/delivery-rules/): Why a lead was held back rather than posted. - [Fix HubSpot delivery when it is paused](/help/troubleshooting/hubspot-delivery-paused/): The same shape of problem on the CRM side. ## Frequently asked questions **Do I lose my Slack settings when delivery pauses?** No. A pause keeps the workspace, the channel, the event toggles, and the delivery rules. Resume and posting starts again with the same setup. **Does Embers retry a Slack rate limit?** Yes. Rate limits and Slack server errors are retried up to seven times over about 6.3 days. Only an error that retrying cannot fix pauses the install. **Why can I not see the Resume button?** Resume shows under Needs attention only while the install is paused, and only workspace admins can open the Slack page. Ask a workspace admin.