Hi @brian
I'm guessing that you're using multiple instances behind load-balancer or have a reverse-proxy that is sending cached results.
Try looking in the log to see what is happening, when you submit. Admin > Troubleshooting > Logs.
Hi @flamber
Actually I am running a single instance. In logs, the only messages related to Slack:
BUG metabase.server.middleware.log
DEBUG metabase.server.middleware.log PUT /api/slack/settings 400 10.0 s (0 DB calls)
{:url "https://slack.com/api/conversations.list",
Thanks @flamber, it was indeed a firewall / DNS issue. That is resolved and I have successfully enabled integration however, the metabase_files channel does not appear in the channel list. Is there a delay due to propagation?
@brian I think you've skipped a step, so it didn't complete adding the app the system channel (metabase_files), which should be public and not used by humans. In other works, you should not post to that channel.
Delete the Slack setup in Metabase and do it again. Check the logs for progress. https://www.metabase.com/docs/latest/administration-guide/09-setting-up-slack.html
@flamber - I don't believe I am missing any steps. Upon saving, a 400 error is observed in the Network logs. Subsequently, the app is unable to find the new channel name. Navigating away from the Slack page and back shows the channel setup to the default "metabase_files".
Logs:
XHRPUThttp:///api/slack/settings
[HTTP/1.1 400 Bad Request 16220ms]
PUT http://api/slack/settings
Status
400
Bad Request
VersionHTTP/1.1
Transferred1.23 KB (54 B size)
Referrer Policystrict-origin-when-cross-origin
Request PriorityHighest
Form submission error:
Object { status: 400, data: {…}, isCancelled: false }
Form.jsx:216:14
e Form.jsx:216
u runtime.js:63
_invoke runtime.js:293
x runtime.js:118
ct StandardForm.tsx:32
l StandardForm.tsx:32
(Async: promise callback)
ct StandardForm.tsx:32
a StandardForm.tsx:32
st StandardForm.tsx:32
st StandardForm.tsx:32
a Form.jsx:64
Redux 3
e Form.jsx:44
u runtime.js:63
_invoke runtime.js:293
x runtime.js:118
ct StandardForm.tsx:32
a StandardForm.tsx:32
st StandardForm.tsx:32
st StandardForm.tsx:32
C ActionButton.jsx:67
React 12
unstable_runWithPriority scheduler.production.min.js:19
React 3
Object { status: 400, data: {…}, isCancelled: false }
ActionButton.jsx:80:18
C ActionButton.jsx:80
(Async: promise callback)
C ActionButton.jsx:68
React 12
unstable_runWithPriority scheduler.production.min.js:19
React 3
XHRPUTht000/api/slack/settings
[HTTP/1.1 400 Bad Request 16220ms]
PUT http://api/slack/settings
Status
400
Bad Request
VersionHTTP/1.1
Transferred1.23 KB (54 B size)
Referrer Policystrict-origin-when-cross-origin
Request PriorityHighest
@brian Not besides creating a custom build. It would be great if Slack allowed some type of way of asking the channel in a different way. We have to use this way, since there's not other API endpoints available.
Anyway, manually add the App to the system files channel: https://github.com/metabase/metabase/issues/23229#issuecomment-1151210508
@flamber appreciate all the timely replies. I have seen all of these postings i searching for a solution and have been manually adding the bot to various channels in that way in trying to set up. Are you saying I should use the "metabase_files" channel, or any channel of my choosing?
@flamber Progress made. I was able to successfully set up integration leveraging one of the channels that I'm guessing is in the first 10k. Metabase now shows the app / bot setup with this customized channel name (not metabase_files). I am able to send pulses to this channel. New question, are we still supposed to be able to interact with the MetaBot with commands that worked in the past, such as metabot help, metabot list, metabot show? If so, that is not working yet.
@brian MetaBot has been completely removed, when the Slack API integration had to be hastily upgraded in January after they deprecated our old integration with just a few days notice.