Torgeir L

> Are you using plain bot scope or the new granular scopes? I'm using the old, plain bot scope. How would that effect the gracefulness of this error? :confused:

> I've got a tentative solution here #1463. Would you be able to test it on your setup @torgeirl ? @nzlosh: I tested it out, but it didn't change anything....

OK. Thanks for taking the time to look into this!

Updated the opening post with my current environment and included the `slackv3` backend as a workaround to help users finding this issue when looking for answers. I do hope this...

> I recommend trying it before 20/09/2022 so you have time to adjust to any differences between the old slack backend and the slackv3 version. @nzlosh: is there a rough...

> The slackv3 backend will probably remain outside the errbot core repository. This allows the backend to have an independent release cycle which allows the backend to fixed quickly since...

> There are many different options for deploying and running Errbot, but Docker seems to be among the more discussed strategies. I suggest that we add some documentation about some...

> Would you be able to provide a small plugin sample code on how you are using these? Pseudo code below; working example code can be found [here](https://github.com/torgeirl/tradingpost-errbot/blob/master/plugins/tradingpost-errbot/tradingpost.py) (the `!card`...

Update: not sure why and when (starting last few perhaps?), but `send_card` have switched from not replying in-thread to reply-in-thread all its responses. So when invoked from a Slack thread...

> Do you mind opening an issue under the slackv3 repository please? Done! I'll keep this one open for now, as this issue with `send_stream_request` remains unchanged.