<?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/83933d3b0f0f4bba8961082ec4891b28&quot; frameborder=&quot;0&quot; width=&quot;2557&quot; height=&quot;1918&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1918</height><width>2557</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1918</thumbnail_height><thumbnail_width>2557</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/83933d3b0f0f4bba8961082ec4891b28-d0a094f86322a792.gif</thumbnail_url><duration>37.843</duration><title>Troubleshooting Suburb Flow Issues in Cloud Version</title><description>In this video, I discuss an issue I&apos;m facing with the suburb flow feature, where it processes items one at a time instead of all at once, making it very inefficient. I mention that in the cloud version, there are options for five or twenty available slots, but I&apos;m currently not utilizing that. I&apos;m looking for solutions to improve this workflow. If anyone has suggestions or insights on how to resolve this, please share your thoughts. Thank you!</description></oembed>