You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@app.event("team_join")
and @app.event("user_change")
to detect any new users added to the team or any updateds for the user
In case of failure in handling the events due to some issues in our internal logic, I'm getting repeated events request from slack, want to know how to avoid these in case of failure in handling the event.
Reproducible in:
slack-bolt==1.9.1
slack-sdk==3.11.1
The text was updated successfully, but these errors were encountered:
Hey @mohan-raheja - You can register an app.error callback, a global error handler. Errors of type BoltError and others error types (from your app) will cause this middleware to run, and there you may set the BoltResponse status and headers yourself. Here's an example
You can try using this to set X-Slack-No-Retries header to turn retries off, for instance. https://api.slack.com/apis/connections/events-api#retries-off
Another approach is to have a custom global middleware that checks the retry-num in a request. As I mentioned at #731 (comment), it is not generally recommended (because resolving the timeouts is ideal). That being said, if the approach works well for your use case, it's an option too.
I'm using slack events in my app
@app.event("team_join")
and @app.event("user_change")
to detect any new users added to the team or any updateds for the user
In case of failure in handling the events due to some issues in our internal logic, I'm getting repeated events request from slack, want to know how to avoid these in case of failure in handling the event.
Reproducible in:
slack-bolt==1.9.1
slack-sdk==3.11.1
The text was updated successfully, but these errors were encountered: