<?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/c8d9436fd39f47caac11f73fd3ca1614&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c8d9436fd39f47caac11f73fd3ca1614-cbad61cc0e1c9a9c.gif</thumbnail_url><duration>273.2982</duration><title>Addressing Duplicate Order Issues with GoTranscript 📂</title><description>In this video, I walk through our V4 make scenario, highlighting the watch event webhook that triggers when a file is ready. We make an API call, and depending on the video&apos;s language, we send it to a different transcript service, GoTranscript. I&apos;ve noticed some issues with duplicate pings resulting in multiple orders being submitted, which we usually catch and cancel promptly. I review specific instances of these duplicates, including timestamps and file details, to understand the problem better. Please keep an eye on this issue and let me know if you have any insights or suggestions.</description></oembed>