The case is after authorization, I get the access_token and refresh_token and then distribute the same copy of tokens to different runtime instances. And I'd like to let each runtime instance to have separated token refresh cycle.

After the access_token is expired, there will be token refresh request happened in different instances. So the questions are:

1. Since the refresh_token is same, will be the new generated access_token still same in different instances?

2. If same, then I can consider it's same session right?

The case is after authorization, I get the access_token and refresh_token and then distribute the same copy of tokens to different runtime instances. And I'd like to let each runtime instance to have separated token refresh cycle.

After the access_token is expired, there will be token refresh request happened in different instances. So the questions are:

1. Since the refresh_token is same, will be the new generated access_token still same among different instances?

2. If not same, that means there might be a lot active access tokens. As per Salesforce, one connected app can only have maximum 5 active access tokens https://success.salesforce.com/answers?id=90630000000Cy3EAAS&feedtype=RECENT&dc=All&criteria=OPENQUESTIONS& Then some of running instances will have issue to subsequent REST API call?