Hello, we are trying to improve our application’s performance by implementing caching into our Action Triggers– to minimize our token generation calls. We were successful on getting it stored with a 24-hour expiration schedule; however, upon our next run it seems that the stored value was gone.
I have no idea if this is a limitation, if does, are there any settings that we can change in order to carry over our caches?
Thank you
Action Triggers in your application may not be designed for persistent caching across runs. The cache is likely cleared after each trigger execution, as it’s meant for temporary data within a single, short-lived session rather than for long-term storage. To carry over data, you’ll need to use an external storage solution.
Hi @denmark.daya, and thank you for the question.
As @eva55anderson mentioned, the behavior you’re observing is expected. The cache available within an Auth0 Action (actions.cache) is non-persistent and is designed to only last for the duration of a single login transaction. To store data that persists between logins, you should use app_metadata on the user’s profile.
Here is a link to our docs on Application Metadata.
I hope this helps you solve your use case!
Kind regards,
Teodor.