{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9f51f946b3ac4b249c71187d32b2bbd9\" frameborder=\"0\" width=\"1108\" height=\"831\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":831,"width":1108,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":831,"thumbnail_width":1108,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9f51f946b3ac4b249c71187d32b2bbd9-af8d3561b0330ff6.gif","duration":196.668,"title":"Struggling with Custom Authentication in Retool 🤔","description":"Hi there, my name's Matt, and I'm reaching out because my company recently acquired Retool, and I've been having some challenges with custom authentication. Specifically, I'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've confirmed that my refresh token is valid and works when tested directly, but it isn't executing as expected during API calls. I've followed the documentation closely, but it just doesn't seem to work as described. If anyone has insights or solutions to this issue, I would greatly appreciate your help!"}