video1.0<iframe src="https://www.loom.com/embed/274b0d05a4484acc96938cbc7452a2b8" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/274b0d05a4484acc96938cbc7452a2b8-8709ea0213c44950.gif435.963In this Loom video, I walk you through an issue with your workflow that ends at the ASCII note due to errors caught by the error shield, preventing further execution. The main problem arises because the Gmail Reader Node is not producing any attachment outputs, leading to empty iterations in the Split Text Node. I suggest checking if attachments are present before filtering and propose a solution that involves merging the attachment outputs and creating two branches in the workflow: one for processing attachments and another for handling cases with no attachments. If you have any questions or need further clarification, feel free to reach out. I’ll share the updated workflow with you for your review and implementation.