My current problem is having a flow with some http requests and calcs that is working well while receiving data between intervals, that give it enough time to process and finish.
But I have seen that receiving data very fast, it begins processing the flow without finishing the previous one.
It looks nice in the begining, but the flow goes to a system that requrires an API Token with steps
So, in this scenario, receiving lot of data very fast, login is executed multiples times and the remote server resets the connection.
There is an option that is to get an unique login and conserve the token for few hours without logout
Looks a good option.
My question is:
Where do you think is the best place to store the token to query it in every event of receiving batch data ?
I have tested context but it doesn't remember the previous value in a new data entry.