Adding A slack notification or trigger does not work

[jupeeter8]

Bug:
When adding notification rule for a schedule or escalation policy the UI shows "unexpected error": Logs Mention missing scope

Logs:
AuthUserID=387cc228-ace3-4a10-b61a-226e513e6359 RequestID=7dcf0686-aab8-472c-a6e4-5cd73fdb425a error="input: setScheduleOnCallNotificationRules missing_scope" host=<host_address> http_method=POST http_proto=HTTP/1.1 referer="<host_address>/schedules/0c98347c-19b3-4973-910d-3bc320eb8b78/on-call-notifications" remote_addr="127.0.0.1:43340" uri=/api/graphql x_forwarded_for=<client_ip> x_forwarded_host=

Scopes For the bot

Slack credentials are correctly configured

This is how goalert was setup
I have an VM where go alert is already running.

1. Took a database dump of the existing go alert
2. Created a new DB and restored the dump to it
3. Started another instance of go alert on a new VM with the new DB
4. Created a new Slack Bot
5. Updated the slack configs in the go alert tool

[mastercactapus]

Have you tried using the manifest YAML to configure the application in Slack?

Here's the current list of scopes in that template:

oauth_config:
  scopes:
    bot:
      - links:read
      - chat:write
      - channels:read
      - groups:read
      - im:read
      - im:write
      - users:read
      - users:read.email
      - usergroups:read
      - usergroups:write
      - team:read

[jupeeter8]

@mastercactapus Thanks for the input, I'll try this out and see if it works

[jupeeter8]

@mastercactapus This did not work either, I got it to work by not changing the slack bot. This way i am able to get notifications to the slack but the unexpected error issue is still there.