Regarding Access and Refresh Token Behaviors

Hi , 
In our SugarCRM application we are having 3 instances and they are behaving differently .

BEFORE

Please find the query we have raised earlier regarding Invalid access token and refresh token (https://sugarclub.sugarcrm.com/dev-club/f/questions-answers/5704/facing-invalid-refresh-token-issue)

The scenario was with all the 3 demo instance and credentials

On first environment , if we test connection ,will get access token a1 and refresh token r1

On Second environment with same demo instance and same credentials if i tried to execute test connection parallelly, we will receive new access token  a2 as well as new refresh token r2 

first environment received  access token a1and refresh token r1 will become invalid.


NOW

for the 1st instance 

after creating another connection with same credentials new access token a2 and refresh token r2 is created but also the first connection is working fine with the old access token a1 and refresh token r1. we are not receiving invalid access token and refresh token as earlier.

for the 2nd instance and 3rd instance 

after creating another connection with the same credentials the first connection is failing because of the above mentioned scenario. we are getting invalid access token and refresh token error as earlier.



Is there any recent changes in the SugarCRM application ?. If there is any changes happened can somebody please mention those here.