I have two Oauth2 accounts (Munchkin ID:792-XXXXXXX) and (Munchkin ID:650-XXXXXXXX) . 729 Account worked as expected without any errors, but when working with 650 account, I always get 601 exception even when using new access token also. Could you please tell me what I can do to fix this issue? or else resolve this from your side ?

Need some more context here. Why don’t you show either (a) the app code you’re using to fetch the token and call Describe Lead, or (b) a screen recording showing fetching the new token and then hitting the Describe endpoint.

Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

I always get a 601 error when using Oauth2 credentials, even though I used the latest access token

It’s not a refresh token, it’s an access token.
Type should be set to Bearer Token if you’re doing it this way in Postman.
Please inspect/show the actual header that went on the wire, not the Postman UI shortcuts.

I always get a 601 error when using Oauth2 credentials, even though I used the latest access token

Re: I always get a 601 error when using Oauth2 credentials, even though I used the latest access token