Slack slash command failed with the error "dispatch_failed"

[stulwilliams]

Hello.  I'm trying to build a simple "Suggestions Box" slash command in Slack and use Power Automate to document the suggestions we receive to a SharePoint list.  Here is the desired outcome:

1. Slack user types: /suggestion This is a sample suggestion.
2. Slack user gets a response: Thank you for your suggestion.
3. Suggestion text is recorded to a SharePoint list.

I'm through steps 1 and 2 just fine. I'm using "When a HTTP request is received" as my trigger, then I give a 200 response, parse the JSON, filter the information I want to keep, then make a HTTP post request back to the response_url specified by Slack.  That's all great.

As soon as I add any other action and save my flow, all of the sudden, my slash command won't even trigger the flow to run. Instead, Slack gives me a message: /suggestion failed with the error "dispatch_failed".  I've even tried just adding a simple action completely unrelated like sending myself an email with no collected information, and I get the same response.  The flow doesn't even run, and Slack gives me that error.  If I remove the last action, save, and test again, it all runs perfectly.

Thanks in advance for any assistance!

***EDIT*** Upon further troubleshooting, it appears that I can add some extremely simple actions that do not require a connection, but any action that requires a 365 connection causes the HTTP Request to not trigger.  Examples I've tried include: Create Item (SharePoint), Send an Email, Post Message (Slack), Get User Profile (365), etc.   Actions that do not cause the trigger to fail are simple actions like Compose and Initiate Variable.

[automaton]

Experiencing similar issues. I can't find any information on this issue elsewhere.

It seems that flow won't allow slack slash command triggers when the flow contains certain actions / connectors. Difficult to troubleshoot.

[JimbotronEpicor]

Has anyone found a solution to this problem? I'm having the exact same issue. I get "dispatch_failed" in Slack, and PowerAutomate doesn't even log any attempt to run the flow. It's critical for me to get this fixed.

[thesoupgod]

We were running into the issue shown above. What we did as a work around was to setup a second power automate Flow. So Slack sends to the first flow, where we parse out the needed information, and pass it on to a second flow that takes care of the m365 stuff. Not sure why this works, but it does.

Both flows have a http trigger. 

[Jimbotron5000]

Thanks! That's what I ended up doing and it works. Very strange bug, though. Simply adding a "Create a To Do item" step breaks the entire flow.