You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in every token, if the token grant type is equals to client_credentials, password, authorization_code or refresh_token, it will proceed for action execution.
Before the action execution, first it fetches the action from the DB. If there is an action is configured, that value will be added to cache.
But if action is not configured, the system will have to perform DB queries in every token call to fetch the action.
This will be an additional overhead for the organisations which are not configured actions.
Suggested Improvement
We should find a way to limit DB queries when no action is configured.
Ideally we may need to have a cache in the action execution service and need to invalidate the cache, when an action is added/updated or deleted.
Version
7.1.0
The text was updated successfully, but these errors were encountered:
ashanthamara
changed the title
Limit DB querying to fetch Action in token calls when no Action is configured
Limit DB queries to fetch Action in every token call when no Action is configured
Feb 20, 2025
Current Limitation
Currently, in every token, if the token grant type is equals to
client_credentials
,password
,authorization_code
orrefresh_token
, it will proceed for action execution.Before the action execution, first it fetches the action from the DB. If there is an action is configured, that value will be added to cache.
But if action is not configured, the system will have to perform DB queries in every token call to fetch the action.
This will be an additional overhead for the organisations which are not configured actions.
Suggested Improvement
We should find a way to limit DB queries when no action is configured.
Ideally we may need to have a cache in the action execution service and need to invalidate the cache, when an action is added/updated or deleted.
Version
7.1.0
The text was updated successfully, but these errors were encountered: