Skip to content
Solução de problemas Admin manager

Channel name changes aren't reflected in Dailybot

Channel name changes aren’t reflected in Dailybot

You renamed a Slack channel, Discord channel, or similar destination in your chat tool, but Dailybot still shows the old name in dropdowns or settings. The integration is usually still pointed at the correct place — Dailybot is showing a cached label.

Quick check

  • Confirm delivery — Send a test report or reminder to the destination; if it arrives in the renamed channel, mapping is correct and only the label is stale.
  • Reload the page — Hard refresh your browser or close and reopen Dailybot settings.
  • Wait for sync — Allow several minutes after a rename for the next sync cycle.
  • Re-open the picker — Close the channel selector and open it again so the UI refetches options.
  • Avoid duplicate setups — Make sure you did not create a second workflow still targeting a retired channel name.

Common causes and fixes

Cached channel metadata

Chat platforms identify channels by internal IDs. When you rename a channel, the ID stays the same. Dailybot may keep displaying the previous display name until the next full refresh of channel metadata. That does not mean reports are going to the wrong place. If posts still land in the right channel, you can ignore the stale label until it updates, or use the steps below to force a refresh.

How to force a refresh

First, ensure Dailybot remains a member of the renamed channel. Then:

  1. In Dailybot, navigate away from the workflow or integration screen and back.
  2. Clear your browser cache only if a normal reload does not help.
  3. If your organization policy allows, disconnect and reconnect the chat platform under organization settings — this rebuilds the channel list from scratch. Coordinate with your admin before disconnecting, since it can briefly affect live workflows.

Multiple channels with similar names

After a rename, you might see both an old and new label if the platform briefly exposes duplicates during migration. Pick the entry that matches the channel where the bot currently lives. If you are unsure, compare channel IDs in your platform’s admin tools or ask support to verify the mapping.

If none of this worked

Share with support:

  • Old name, new name, and platform
  • Whether messages still deliver to the correct channel
  • Screenshots of Dailybot’s UI showing the wrong label
  • Approximate time of the rename

We can confirm the underlying channel ID and correct any mismatch.