Murat Doganer
Murat Doganer
Ah it was the second one! The channel wide one where colleagues can leave comments :) Ill give that a go, thank you!
I think with combination of the workaround you added + the default we are good! we just wanted to expand on a few more details - I didnt realise we...
Everyone will be F5'ing today :D
We all really appreciate it @GDay
Hey @GDay loving v2! It looks so gorgeous! Ran into a slight issue with the slackbot, Ive updated the url as suggested above, but the bot itself has completely stopped...
@GDay Yup done those! I've just deployed with heroku to test a new integration and it worked fine, so maybe it had some trouble migrating?
@GDay Interesting, no it does not. Nothing comes up in the logs at all I did use the new token under the SLACK_APP_TOKEN env, sockets are on, maybe ill try...
Ah I was missing the first bit of the `SLACK_BOT_TOKEN`, i've added it in and I am seeing activity from the bot now in the logs However trying to run...
So I've reverted back to the old urls, still no slackbot responses but, i do now see the correct message in the logs `[08/Jul/2022:16:22:10 +0000] "POST /api/slack/bot HTTP/1.1" 200 0...
Yes you are correct, I did indeed get back `1`