<?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/c43060725515427ba506d59aa9b25582&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/c43060725515427ba506d59aa9b25582-80c7ac440132f8c4.gif</thumbnail_url><duration>231.243</duration><title>Fixing Candidate Selection and Pipeline Lookup</title><description>Hey, I walked through two bugs. In the first pod, the code meant to catch an empty candidate list uses length greater than 0, so an empty list skips the error and then hits an index error, and even a valid single candidate can be treated as missing. The fix is to change greater than to equal sign and fix a small spacing typo. In the get pipeline ID function, the loop condition lets it keep paging even after finding the pipeline because only one side of the condition controls continuing. No action is requested from you.</description></oembed>