While configuring the Refresh Auth Workflow, I encountered what seems to be a discrepancy between the official documentation and the observed behavior.
The issue I am currently experiencing is that when an error occurs in Retool, if an error occurs when sending an API request in Retool, the server registers two requests, resulting in my user receiving two failure logs.
As per the Retool official documentation, automatic retry upon encountering errors is intended for 401 and 403 status codes. However, in my experience, it appears that automatic retries are being attempted for all types of errors during API requests.
- Reference Link : Custom API authentication | Retool Docs
I would appreciate clarification on whether this behavior is intentional or if there might be an issue with my configuration. Additionally, I am interested in understanding if there is a way to selectively disable automatic retries, especially for error scenarios other than 401 and 403.
How can I prevent automatic retries for 4xx errors when configuring the Refresh Auth Workflow?
I understand that your team's time is valuable, and I appreciate any guidance or insights you can provide on this matter. Thank you for your attention, and I look forward to resolving this query to ensure optimal usage of Retool for my project.