Caching M2M access token in Actions

[rueben.tiow]

Hi @saiful1991,

Thank you for your reply.

@saiful1991

I added this Action(which I mentioned earlier) to either retreive the cached token or new token. But when I request for an access token from my API, it waits about 15 to 20 seconds and returns 500 error. I found the following error: Error on credentials-exchange: 500 Script execution time exceeded in the log, and my log is bloated with error messages. It seems my API request created a loop of triggers.

Yes, the execution timeout exceeded error can happen if your execution flow takes more than 20 seconds to run. See below:

(Reference: Action limitations)

@saiful1991

Any additional parameter needed to be added on request header while added an Action to the flow?

No, there is no need for additional parameters in the request header.

I also recommend using the Real-time Webtask Logs Extension to debug your Action scripts if they are exceeding 20 seconds.

@saiful1991

Action stays between the Machine-to-Machine flow: Token Requested → Action → Token Issued. If an access token is created in the Action using ManagementClient, then how and what an Action should trigger as a response? Which API Object should be triggered in this case?

Could you please clarify what you would like to do with your cached token?

Note that the access token created in the Action is not the same token issued to the application performing the Client Credentials flow.

I look forward to your reply.

Thanks,
Rueben