<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=429720) </details> <!--IssueSummary end--> ### Summary Currently, the Slack app (on SaaS) integration works when following the [set up instructions](https://docs.gitlab.com/ee/user/project/integrations/gitlab_slack_application.html). However, when it seems if the Slack channel name is updated in Slack the integration is broken and an error for "Connection fail. Check your integration settings. Unable to post to #slacmchannelname, please add the GitLab Slack to any private Slack channels. ### Steps to reproduce 1. Integrate Slack app and add to a channel 2. Change the Slack channel 3. Go to Settings \> Integrations page, then error should show up ### Example Project ### What is the current _bug_ behavior? * Error for "connection failed" when Slack channel name changes ### What is the expected _correct_ behavior? * Slack integration should connect seamlessly even if the channel name changes ### Relevant logs and/or screenshots ### Output of checks #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`) </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes