# Control node execution order **URL:** \ **Category:** Questions\ **Tags:** core, merge\ **Created:** [April 23, 2023, 2:33pm UTC](https://community.n8n.io/t/control-node-execution-order/25509 "2023-04-23T14:33:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![JUVOJustin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/juvojustin/32/14416_2.png) [@JUVOJustin](https://community.n8n.io/u/JUVOJustin)\ **Post date:** [April 23, 2023, 2:33pm UTC](https://community.n8n.io/t/control-node-execution-order/25509/1 "2023-04-23T14:33:47Z")
I have created the following workflow section. How can i make sure the first line of nodes finished even if the second one fails? In this case it basically separates if a create or update operation needs to be executed. ![Bildschirm­foto 2023-04-23 um 16.27.33](https://europe1.discourse-cdn.com/n8n/original/3X/6/e/6e7ec70cf30f15c7a8f395b8511c406158358dd8.png) ## Information on your n8n setup - **n8n version:0.225.1** - **Database (default: SQLite):postgres** - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** - **Running n8n via (Docker, npm, n8n cloud, desktop app):cloudron** ---
**Author:** ![pemontto](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/pemontto/32/2684_2.png) [@pemontto](https://community.n8n.io/u/pemontto)\ **Post date:** [April 23, 2023, 8:16pm UTC](https://community.n8n.io/t/control-node-execution-order/25509/2 "2023-04-23T20:16:01Z")
In the node settings for your http request you can ignore errors. Otherwise if you need to see failed workflows, a hacky way is to just put a couple of No Operation nodes before your troublesome http request to ensure it runs last ---
**Author:** ![JUVOJustin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/juvojustin/32/14416_2.png) [@JUVOJustin](https://community.n8n.io/u/JUVOJustin)\ **Post date:** [April 23, 2023, 8:56pm UTC](https://community.n8n.io/t/control-node-execution-order/25509/3 "2023-04-23T20:56:29Z")
Thank you very much 🙂 Is there no better way than turning off error handling or a relatively ugly workaround? I though maybe there is a magical combination of using merges. But that was my hope speaking 😃 ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [April 25, 2023, 9:05am UTC](https://community.n8n.io/t/control-node-execution-order/25509/4 "2023-04-25T09:05:46Z")
You can also use the Merge node to run your second branch after the first one like so: This uses the _Choose Branch → Wait for Both Inputs to Arrive_ setting of the Merge node: ![grafik](https://europe1.discourse-cdn.com/n8n/original/3X/6/3/63173610a6aa261d5f354e48210b0d0593f99e14.png) ---
**Author:** ![JUVOJustin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/juvojustin/32/14416_2.png) [@JUVOJustin](https://community.n8n.io/u/JUVOJustin)\ **Post date:** [April 26, 2023, 9:31pm UTC](https://community.n8n.io/t/control-node-execution-order/25509/5 "2023-04-26T21:31:11Z")
@MutedJam Thank you very much. The idea i great but since there is an if to separate routes one will very likely never be entered leading to the following state: ![Bildschirmfoto 2023-04-26 um 22.03.18](https://europe1.discourse-cdn.com/n8n/original/3X/7/d/7d0ddefda41f7d025e604c5f601d8287a9e21eb7.png) The final node is never reached due to the waiting for input 1 ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [July 25, 2023, 9:31pm UTC](https://community.n8n.io/t/control-node-execution-order/25509/6 "2023-07-25T21:31:27Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.