<?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/0556984bd9564b328ea4cf413954a514&quot; frameborder=&quot;0&quot; width=&quot;1512&quot; height=&quot;1134&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1134</height><width>1512</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1134</thumbnail_height><thumbnail_width>1512</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/0556984bd9564b328ea4cf413954a514-1693985148018.gif</thumbnail_url><duration>204.005</duration><title>Kestra - issue with dbt cloud trigger job display</title><description>In this video, I discuss the back-end issues we encountered while triggering jobs on the dbt Cloud plug-in. I demonstrate how the tab freezes when clicking on the logs section next to topology, rendering the tab unresponsive. I also suggest a useful feature to display jumps within the logs, similar to dbt cloud, which would allow for easier navigation to models with errors or warnings. Additionally, I highlight the need for better filtering features to identify yellow models and understand the reasons behind warnings and errors. No specific action is requested from the viewers in this video.</description></oembed>