Does the Retry middleware help?

https://hexdocs.pm/tesla/Tesla.Middleware.Retry.html#module-examples

Though I’m not sure if this will let you change the actual request being made, like hitting /oauth/token to get a new token if a request fails…

In my current work, I renew expired tokens (or soon to be expiring) before I do my external network calls. I added that “soon to be expiring” logic after observing some poor alignment in our Oban jobs that ran every 60m and then tokens expiring every 60m … and full pagination capture to go past expiration.

Sorry I don’t have a good solution for you, but wanted to chime in and see what other people say too.

Right now, it is on demand. The module exposes a fetch_user function and to return the full list of users (which may require synchronous paginated results), we renew the token (if needed) and then start paginated requests.

There is an Oban Job that utilizes the module to do its work (which is out of cycle of normal user activity).

If you want to chat about our setup, I’m happy to do a private demo.

I wanted to write such a Tesla middleware, but didn’t have time.

However you might be interested in oauth2_token_manager: it’s very beta, but the goal is to handle token renewal among several actors. Don’t use it in prod, but you can probably get inspiration.

You’ll also have to authenticate to the OAuth2 server when renewing the token. You can use GitHub - tanguilp/tesla_oauth2_client_auth: Tesla middlewares for OAuth2 and OpenID Connect client authentication for this which handles various client authentication schemes.