Slack_bolt sends 200 to failed events about bolt-python HOT 4 CLOSED

@WilliamBergamin

I've read the docs where it says that there is no processing should be done, so i guessed it was the desired behavior of the sdk
For my side i solved it with setting raise_error_for_unhandled_request
and adding something like

@app.error
def handle_error(response):
   response.status = 500

from bolt-python.

@WilliamBergamin When process_before_response is set to False (the default setting), this is an expected behavior. This is not a bug. The issue reporter might notice it afterwards.

from bolt-python.

Ah, I posted my above comment at the same timing!

I meant that, when process_before_response is set to False (when you don't pass the argument to App constructor, the value is False by default), the error within your @app.event listener does not affect the HTTP response status. Responding to a request from Slack would be done asynchronously regardless of your listener execution result. If you desire to return a 500 error when your listener fails, you can set process_before_response=True in App constructor. A downside of this approach is that your listener execution must complete within 3 seconds (this is a requirement by Slack server side).

I hope this clarifies. I'm in a different timezone, so if you have further questions on this, other team members like @WilliamBergamin can help you out during my night time.

from bolt-python.

Thanks @glebkrapivin for writing in 💯

This seems like a real bug, this issue could be a feature request, did you intend to close it?

from bolt-python.