Slack delivery is paused
Fix a revoked token, a missing or archived channel, or a bot that was removed, then resume the install and replay the deliveries you missed.
When Slack returns an error that retrying cannot fix, Embers stops posting instead of hammering a dead channel. The Slack card on Settings, then Integrations (/settings/integrations) shows a red Paused badge and the reason, in the form Slack paused after not_in_channel.
What pauses an install and what does not
Rate limits and Slack server errors are retried: the first attempt plus seven more, from 30 seconds out to roughly 6.3 days. Only a terminal error pauses the install, and it pauses on the first occurrence.
Fix the reason, then resume
invalid_auth
The stored bot token is no longer accepted. This normally means the Embers app was removed from the Slack workspace, or the Slack workspace itself changed. Reinstall: choose Connect Slack on the Integrations screen and approve the app again, then pick the channel.
token_revoked
Someone revoked the token from the Slack side, usually a workspace admin cleaning up apps. Reinstall the same way. Reinstalling on an existing account keeps your event choices rather than resetting them.
channel_not_found
The channel Embers was posting to no longer resolves. It was deleted, or the bot lost the visibility it needs to see it. Pick a channel again on the Integrations screen. Public channels list automatically; a private channel appears only after the Embers bot has been invited to it.
not_in_channel
The bot was removed from the channel it was posting to. Open that channel in Slack and invite the Embers bot back with /invite, then resume. Nothing needs reinstalling.
is_archived
The channel was archived. Unarchive it in Slack, or choose a different channel on the Integrations screen.
A few rarer Slack errors are also terminal, including an expired token, an inactive workspace, and enterprise key management or workspace grants being withdrawn. They all follow the same shape: fix it in Slack, then resume in Embers.
Resume and replay
-
Fix the cause in Slack
Reinstall the app, invite the bot, unarchive the channel, or pick a new one. Resuming without fixing the cause pauses the install again on the next delivery.
-
Press Resume
The Slack card shows a Resume button while the install is paused. It clears the pause and keeps your workspace, channel, and event toggles exactly as they were.
-
Send a test
Use Send test. It posts a card built by the same code as a real delivery and creates no CRM record, so it confirms the fix without waiting for the next lead.
-
Replay what you missed
Open the delivery history on the Slack card. Deliveries in a failed or blocked state have a retry control. Retry is only available once the install is no longer paused and is enabled.
Reading the delivery history
Each row records the event type, the state, the Slack error, the HTTP status, the attempt count, and when the last attempt ran. History is kept for 30 days. If several rows carry the same error, fix that cause once rather than retrying them individually, then replay.
Deliveries that already posted are never posted twice: Embers stores the Slack message timestamp and skips anything that has one.
Still paused after resuming
- The install pauses again immediately: the cause was not fixed. Read the new pause reason, it may be a different error than the first one.
- The channel is private and the bot was never invited: invite it, then pick the channel again.
- You are not an administrator on the account: the Resume button is not available to you. Ask an account administrator.
If none of that applies, email the pause reason and the time to viraj@useembers.com.
Related
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.