Happy to help, @bayuser!
I’m not sure why this happened after 2.5 days specifically. Were any other sessions created/ended with the user you are testing with? For example, if you log in with a user in Firefox and then log in with the same user in Chrome and log out of the session in Firefox, then the Refresh Token would become invalid for the session in Chrome.
Are you able to find the error in the tenant logs when this happened?
You can handle Refresh Token exchange errors by initiating an interactive login flow with either loginWithRedirect or loginWithPopup. That is the only way to get a new Refresh Token.