Feature Request: Run The Refresh Directive Automatically When receiving a 401

"I’m currently dealing with a situation where we are utilizing an external OAuth service. While we can generate a new token when a user connects, there is a potential issue when we introduce new scopes. Since the user must authorize these scopes outside of the ‘Make’ process, it can lead to a disruption in the connection.

To address this concern, it would be extremely beneficial if we could implement an automatic refresh directive that triggers when a 401 error is received. This would allow the system to assume that the token has expired and attempt to refresh it without immediately throwing an error.

The addition of this feature not only would provide a smoother user experience but also act as a failsafe in case there are any disruptions in the logic or backend of the application, especially concerning token expiration times.

Thank you for considering this enhancement."

That’s a great idea!

You can submit this suggestion to the Idea exchange, under Platform ideas and improvements. Don’t forget to search for it first, just in case someone already suggested it!


The Idea Exchange portal is preferred for sharing your ideas and feature requests, however, I handed over your idea to our Product Managers.