<?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/d5561fca8ad4452fa0dfffe305884e38&quot; frameborder=&quot;0&quot; width=&quot;1858&quot; height=&quot;1393&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1393</height><width>1858</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1393</thumbnail_height><thumbnail_width>1858</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d5561fca8ad4452fa0dfffe305884e38-662c1ffb5e66e1e9.gif</thumbnail_url><duration>127.582</duration><title>Preventing Duplicate Subrequests</title><description>In this video, I discuss the issue of duplicate subrequests in our scheduling system, specifically highlighting a recent case involving Jenny and Monica. I propose a solution that would allow us to see existing subrequests when creating a new one, which could help prevent these duplicates from occurring. I believe this change would streamline our process and improve efficiency. I would appreciate your thoughts on this solution.</description></oembed>