Caching M2M token in Actions

[rueben.tiow]

Hi @tea.veljkovikj,

Welcome to the Auth0 Community!

I understand that you are trying to cache your M2M tokens in Actions.

Firstly, if you have exceeded your monthly M2M quota, you could be limited from issuing new M2M access tokens. In this case, I recommend reaching out to our direct support channel on support.auth0.com to see if they can help with your quota utilization.

@tea.veljkovikj

Is the access token created in the Action is the same token that is issued to the application performing the Client Credentials flow?

Nope, they are considered different access tokens. Only the access token in the Action can be cached and used in future Action scripts.

@tea.veljkovikj

When caching anything it says that the cache can persist upto 15 minutes, however when I re-run my the flow the cache is always empty and returns a undefined value, the only time when I can access the cache is during the execution of the action or from another action, but in the same execution flow. So, my question is does the cache only work within the same flow?

If you are testing using the Actions built-in debugger interface, you will experience this issue where the cached items do not persist for up to 15 minutes. For cached items to persist, you must initiate the respective flow. For example, you must make a client credentials request for the cached items to be persist. Subsequent client credential requests will persist the cache items for up to 15 minutes.

Reference:

• Caching M2M access token in Actions - #4 by rueben.tiow

Please let me know if you have any further questions.

Thanks,
Rueben