{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6c1a7c6cbed5460d8c9e584854dcab3f\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6c1a7c6cbed5460d8c9e584854dcab3f-c60126f3d1562019.gif","duration":180.607,"title":"Resolving Workflow Errors in Job Application Subflows","description":"In this video, I explain an issue with our workflow related to the if-else condition and how it affects the job application subflow. The jsonReader node is currently set up to execute only when the if-condition is met, which is causing a clash when the else-condition is triggered. I recommend using a join-parts node to handle both the if and else responses, allowing us to process the input regardless of which condition is met. Please take a look at the suggested changes and implement the join-parts node to improve the workflow. Let me know if you have any questions!"}