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
{{ message }}
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
The issue is I'm expecting the original block_action to be replaced by the message Workflow approved by {user}. But this doesn't seem to be happening. Is there something I'm missing? Thanks for your help and providing this library!
The text was updated successfully, but these errors were encountered:
Hi @vallard, thanks for your kind words. I am glad you enjoy the library.
While it is technically possible to use both an event handler and a custom response for the same action, it will yield unexpected results. This is because once an event is received on @actions, it will immediately return an HTTP 200 response to Slack. Your custom response will also be returned, but the request has already been responded to, so it falls on deaf ears.
The solution is to use only one kind of response to a unique action, you have to choose between responder and actions.on. That said, it is possible to make subsequent requests related to the action after responding to slack with 200. There should be an API endpoint to which you can send the action id and the action blocks. Please refer to the Slack developer documentation for further details on that.
Thanks for this great library! I was able to process actions but I'm having issues with custom responses. I have my code that looks as follows:
The issue is I'm expecting the original
block_action
to be replaced by the messageWorkflow approved by {user}
. But this doesn't seem to be happening. Is there something I'm missing? Thanks for your help and providing this library!The text was updated successfully, but these errors were encountered: