<?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/9f51f946b3ac4b249c71187d32b2bbd9&quot; frameborder=&quot;0&quot; width=&quot;1108&quot; height=&quot;831&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>831</height><width>1108</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>831</thumbnail_height><thumbnail_width>1108</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9f51f946b3ac4b249c71187d32b2bbd9-af8d3561b0330ff6.gif</thumbnail_url><duration>196.668</duration><title>Struggling with Custom Authentication in Retool 🤔</title><description>Hi there, my name&apos;s Matt, and I&apos;m reaching out because my company recently acquired Retool, and I&apos;ve been having some challenges with custom authentication. Specifically, I&apos;m facing issues with the automatic refresh of access tokens when they expire, despite having set up a refresh flow that should trigger on 400 or 401 errors. I&apos;ve confirmed that my refresh token is valid and works when tested directly, but it isn&apos;t executing as expected during API calls. I&apos;ve followed the documentation closely, but it just doesn&apos;t seem to work as described. If anyone has insights or solutions to this issue, I would greatly appreciate your help!</description></oembed>