when trigger token call having issue if there already ongoing token call is there, is just don’s last call and wait for first call only and return same value for both call
using this getAccessTokenSilently methods, changes custom_key value for both the call
My understanding is that you are having issues with the getAccessTokenSilently method, where multiple calls are made and you are trying to pass custom_key values that get ignored.
The getAccessTokenSilently method relies on cached tokens and attempts to use those if the token has not expired, without user interaction. Passing dynamic parameters such as custom_key should be added during the login flow or through an Action instead of being passed as a parameter within getAccessTokenSilently.