<?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/9cd82653bacb4528bdaac117ec85a976&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/9cd82653bacb4528bdaac117ec85a976-00001.gif</thumbnail_url><duration>114.29960590900001</duration><title>Carves Bug and Pagination Params [DONT KEEP]</title><description>In this video, I discuss a bug I encountered in the FleetCarves endpoint while working with pagination parameters. I demonstrate how adding pagination parameters affects the results and highlight an issue with the &quot;after&quot; parameter. Additionally, I mention a separate SQL issue that is not related to this particular check-in. Overall, the changes made to the REST API are mostly stylistic.</description></oembed>