SolvedIntegrations
Slack alerts stopped arriving after we recreated the channel
Asked by Rachel OwensJul 15, 2026
We had Slack alerts working fine. Last week we archived the old Slack channel and made a new one, and generated a new incoming webhook URL. I updated the URL in MonoDuty but nothing arrives anymore. The MonoDuty channel is still listed as active.
Accepted answer from MonoDuty Support
40
Selin YıldızMonoDuty Support EngineerJul 16, 2026
That message comes from Slack, not from us, which narrows it down nicely. Slack invalidates an incoming webhook when its target channel is archived, and generating a new webhook in the Slack UI does not update the old one. Here is the fix:
1. In Slack, go to the app configuration for your incoming webhooks and confirm the webhook is bound to the new channel and is listed as active. If it still points at the archived channel, create a fresh one.
2. Copy the full URL. It should look like https://hooks.slack.com/services/T***/B***/*** with three path segments after services. A truncated copy is a very common cause.
3. In MonoDuty, edit the notification channel and paste the URL into the url key of the channel configuration. Save.
4. Fire a test incident, for example from a disposable alert trigger, and re-check the delivery records. A successful delivery is recorded as sent.
One thing to be aware of while debugging: there are no automatic retries. Each notification is attempted once, so the alerts that failed during the broken period are gone rather than queued, and fixing the URL only affects future alerts.
Was this helpful?40 of 42 found this helpful
3 replies
Selin YıldızMonoDuty Support EngineerJul 15, 2026
Hi Rachel, when a Slack destination stops after a URL swap there are usually only two candidates. First, whether the new URL was saved into the right place, and second, whether Slack itself is rejecting the post. Could you open the notification channel in MonoDuty and check its delivery records? Failed deliveries store the error we got back.
Rachel OwensJul 15, 2026
There are entries marked failed and the error says something about no_service or invalid webhook.
Rachel OwensJul 17, 2026
The webhook was indeed still bound to the archived channel. New one works. Thanks for the explanation about retries too.