Closed saurabh0719 closed 1 week ago
Hi @saurabh0719, thanks for asking the question.
A possible cause of the error could be that the token your database stores is outdated for some reason (e.g., the customer reinstalled your app with a different set of scopes and your app failed to store the new one, or your datastore actually stores newer tokens but your authorize code in the bolt app fails to fetch them).
When a bot token is "inactive" and your app's database does not have any other tokens associated with the workspace, there's nothing you can do on your app's side. The only approach to resolve this is to ask your customer to reinstall the app. We won't be able to guess further. I hope this helps and your customer can use your app without any issues soon.
👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.
As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.
(Describe your issue and goal here)
When getting my customers to authorise with my slack bot, I call the
auth_test
method with the newly obtained tokenSlack sent us back an
account_inactive
error. Going by slack's documentationHowever our customer is active on their slack workspace. Also this flow seems to be working for all our other customers, and our own account as well. Can you help me with what could be the list of all possible reasons to get this error? I opened a ticket on your support tool previously regarding the same.
Reproducible in:
The Slack SDK version
Python runtime version
OS info