Comment by Sebastian on "How to handle concurrent API calls using Refresh Token in redux-saga?"

I don’t know redux Saga that much but this would be my approach: assuming that the api calls are wrapped in redux actions and the session timeout is expressed as http error on the request:

Request 1 - error http session invalid or something to read the error - call action method which renews the session token and passes additionally (and optionally) the method to execute after the session has been renewed which is in this case request 1 itself.

This way you can renew the session from every request. I think this should be possible with saga too.

How about the situation when there are 2, 3 or 4 requests made at the same time and the token gets expired? I have to get the new token using the Refresh Token and then call each request. How to handle these concurrent requests?

are they that much concurrent and often? With redux you are aware of the get token request and could pause the other requests until a token arrives. Maybe put them in a list of requests to run, when the token arrives.

Can you provide me a flow for redux actions and state management as whole? Here is the repo I am working on and now I am going to add the refresh token in the API

Link to repo: github.com/ashokdey/blog-saga

I will try it this evening. Basically it’s a chain of dispatching actions.

Search Hashnode