<?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/0bf1eaa6d3374be782eb18859f24e08f&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/0bf1eaa6d3374be782eb18859f24e08f-00001.gif</thumbnail_url><duration>227</duration><title>Investigating a Failing DBT Test Part 1: Find the compiled SQL</title><description>In this video, I will guide you through investigating a failing DBT test. We received a notification in Sentry about a uniqueness test failure on the effect monthly routes table&apos;s key column. I will show you how to find the compiled SQL for this failing test so that you can investigate it. You will need to open a terminal in JupyterLab, navigate to the data info repo, and run &quot;poetry, run dbt compile&quot; to compile all the SQL. Once completed, you can locate the compiled SQL in the data info repo. Stay tuned for the next steps on how to run and investigate the SQL further.</description></oembed>