<?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/40be617c3d5d4ba0b370ad00466b69c6&quot; frameborder=&quot;0&quot; width=&quot;1904&quot; height=&quot;1428&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1428</height><width>1904</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1428</thumbnail_height><thumbnail_width>1904</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/40be617c3d5d4ba0b370ad00466b69c6-0509db78c4d3ddc7.gif</thumbnail_url><duration>295.356</duration><title>Understanding File Object Naming</title><description>In this video, I’m explaining the confusion around the term &quot;attached file name&quot; in our workflow. We&apos;re working on changing it to &quot;attached file&quot; for clarity, as it currently refers to the file object itself. I also demonstrate how to connect nodes in the workflow and address potential issues with flows being disabled after consecutive failures. Please take a look and let me know if you have any questions or need further clarification.</description></oembed>