Updating secret from service - next step (Web requests) uses old secret/ not updated yet

Bugs and feature requests Bugs
, ,
1

Hi,

I’m using a service to get a new token when needed for some web requests. We are experiencing that when a token has expired and the service is updating the secret with a new token, the next step in the main action (web request ) is getting an error “not authorized”, but running the same action again (not updating a new token) is successful.

For me it seems like the orignale action is “to fast” , getting the old secret. Eventhough the service has updated the secret to the latest token.

When I debug it , it seems to work as expected , maybe because it takes longer to move to the next step?

2

Hi Preben,

Sometimes it can take a bit of time to sync between secrets and services. Have you tried adding a sleep action node? This is often useful to take a 100-200ms pause and allow the secrets to be fully updated from the service, before using this secret in the next step.

Rhys