Rank: Newbie
Joined: 5/17/2019 Posts: 2
|
Hi,
We've got a mapping that does an API call to generate an auth token, but unfortunately none of the api response tokens pass the token back. As a result, when we chain two APIs processes together the auth token API call gets re-submitted and a new token is generated.
The API owner allows new tokens to invalidate old ones, but it has to wait a few seconds before this can happen, and they have said this is not the intent. Their intent is to generate a token that has an internal kill of 30 seconds that gets extended every time an api is called using the token.
The workaround is either:
a) separate these API calls and pass through the auth token as a parameter and run each step in concert using flowforce b) add a delete auth token api call to the original mapping that triggers when a success response is received from the first API call.
Is there a setting that allows a variable to be calculated once for an entire mapping? The problem here is that the token doesn't get passed back in the API responses and so have multiple subtargets (The email/auth call goes back to the first step despite setting compute-when to once).
Is there a way to make the first auth token generating API call fire only once per mapping run?
|