<?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/8fc3f55bc2594c30a806cc7cb8dc4c71&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/8fc3f55bc2594c30a806cc7cb8dc4c71-2e7944140f09b68d.gif</thumbnail_url><duration>65.6509</duration><title>tags field with fetch_values_from unstable</title><description>In this video, I explore an interesting issue that arises when using a text field to fetch values from a remote endpoint. I demonstrate how typing speed can affect the results returned; for instance, when I type quickly, I can trigger a situation where no results are returned, even if the backend confirms that nothing is found. Conversely, typing slowly allows the fetch to work properly. I encourage you to pay attention to how input speed impacts the functionality, as this could be crucial for our user experience. Please consider testing this behavior in your own implementations.</description></oembed>