<?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/f6e5479baeef41ef8c1391a6b41b7dfc&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f6e5479baeef41ef8c1391a6b41b7dfc-00001.gif</thumbnail_url><duration>58</duration><title>GraphQL Query Limitations - Bug? - Count for Objects Retrieved</title><description>Hey everyone! I have a quick question for those of you familiar with GraphQL. I&apos;m working on creating a query that looks at a CRM object, but I&apos;m running into an issue where the count maxes out at 500 objects, even though there are 845 objects in the CRM. Even if I remove some properties to lower my use point score, the count remains the same. I&apos;m wondering if any of you know if there is a maximum limit for object retrieval in GraphQL. Any insights would be greatly appreciated!</description></oembed>