Closed britt closed 9 months ago
Hi @britt, thanks for writing in! However, the same situation does not arise for me (I verified that the latest version works for me). If you find a specific condition to reproduce the unexpected behavior, please let me know the way to reproduce it.
@seratch You are right. I wrote a simplified version to reproduce the bug that just slept while the Ack handler returned and it worked fine.
Slack documentation says that you need to acknowledge a slash command to prevent it showing a timeout error to the user after 3 seconds, but slack-edge terminates the
SlashCommandLazyHandler
as soon as theSlashCommandAckHandler
completes.Below is a contrived example. I discovered this when trying to call an API function that took several seconds to complete.