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

New Participant

Question

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

Forum|Forum|3 years ago
September 30, 2022
2 replies
2902 views

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 ?

Marketo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

SanfordWhiteman

New Participant

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.

New Participant

@sanfordwhiteman I generated new access token by using postman and calling endpoint by using postman but it failing always with 601 and the same way is working with different Oauth2 credentials.

SanfordWhiteman

New Participant

Please show the full HTTP headers (i.e. Authorization header) that went on the wire.

New Participant

Few months before it working fine but now it always throwing 601 exception