<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/6c1a7c6cbed5460d8c9e584854dcab3f&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/6c1a7c6cbed5460d8c9e584854dcab3f-c60126f3d1562019.gif</thumbnail_url><duration>180.607</duration><title>Resolving Workflow Errors in Job Application Subflows</title><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!</description></oembed>