# Continue on after Error Running Node

**URL:** https://forums.losant.com/t/continue-on-after-error-running-node/461
**Category:** Feature Request
**Created:** [April 5, 2017, 2:55pm UTC](https://forums.losant.com/t/continue-on-after-error-running-node/461 "2017-04-05T14:55:25Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Matthew\_Alsobrook](https://avatars.discourse-cdn.com/v4/letter/m/e19b73/32.png) [@Matthew\_Alsobrook](https://forums.losant.com/u/Matthew_Alsobrook)
#### Post date: [April 5, 2017, 2:55pm UTC](https://forums.losant.com/t/continue-on-after-error-running-node/461/1 "2017-04-05T14:55:25Z")

</div>

Currently, if there is an error during the workflow, the workflow will stop. We experience this sometimes when an http request or lambda function call times out. Would it be possible to have a continue on error option or add nodes like them an error path from the node (like a conditional node but one path on error). This would allow us to add in additional error handling that would be extremely helpful.

---

<div class="post-metadata">

### Author: ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)
#### Post date: [April 5, 2017, 3:03pm UTC](https://forums.losant.com/t/continue-on-after-error-running-node/461/2 "2017-04-05T15:03:27Z")

</div>

This is a good feature request. We’ve been thinking up ways to add better error handling.