Lindy Community Icon

Home
Events

00 Announcements
01 General
02 Support
03 Bugs
04 Requests and Feedback
05 Share Your Lindy
06 Intros

Community Guidelines

Troubleshooting Guide

Powered by Tightknit

Preventing Workflow Shutdown from Single Action Failures

·Jul 23, 2025 02:29 AM·

^ this doubles as a support request as well... how can I ensure the entire flow doesn't shut down due to one Action failing?

9 comments

· Sorted by Oldest

Ronnie P.
·
·
Same issue on my end. Would love to see more error handling options.
✍️1
David V.
·
·
Agreed! When my HTTP request webhook fails it just stops the entire process, there's no option to continue anyways.
✍️1
Marvin A.
·
·
great, feedback. we have been talking about error handling A LOT internally. I’ll share it with the team. We will def do something about it soon. 🙏🏾
💯2
David V.
·
·
Great thanks! Encountered this again with a discord message failing to send, which stops the entire flow. Any updates by chance Marvin A.? Or any ways to get around this? A condition loop to check for failure doesn't work because the errors stops the flow entirely, which makes sending messages to discord/slack a dangerous addition to add to a flow because if that fails, everything else after fails. Thanks for checking in for me!
✅1
Marvin A.
·
·
Not yet — but we’re spending the majority of the next few weeks/months on stuff like this
Marvin A.
·
·
whats the exact use case? the error ideally shouldn’t happen in the first place
Marvin A.
·
·
happy to look into it if you share the task url!
David V.
·
·
Gotcha, thanks! A simple checkbox for HTTP requests actions and discord/slack actions that forces it to continue down the flow even if it errors out would be great. Use case is just simply sending a discord message with a report from the agent. https://chat.lindy.ai/veganhacktivists/lindy/violet-apps-review-current-68801d64eceea457d2a12b98/tasks?task=68a3db17195dcbe961063602 Sometimes it works, sometimes the discord message errors out like this. When this happens, we miss the entire report which is pretty bad.
David V.
·
·
Thanks for looking into it!