Forum Discussion
Thanks @ddellsperger . I still see the same issue after unchecked the “Send Client Data as Basic Auth header” and also removed the auth endpoint config.
I did Authorize and the tab opened and updated and then did the “Apply” button.
I have attached the error log file.
Errors_GetAllLeads-2022-08-23T10_53_11.667.json (805 Bytes)
Which snap are you using to accomplish this, are you simply using a Rest GET/POST to obtain this data, or are you using the Marketo Snap Pack itself? Do you maybe have a pipeline screenshot that I could look at here, it seems like you’re running a series of Rest snaps to get paginated data. I remember Marketo being somewhat unique, in their documentation they state:
If you call the Identity endpoint before your token has expired, the same token and the remaining lifespan will be returned in the response.
This means that our refresh process doesn’t work the same way for Marketo as it might for other systems. Because they return an error with a value 602 rather than a http status code of 401 or 403 for an expired access token, they have to be treated somewhat differently. This is accounted for in our Marketo Snap Pack, but since this error message system that Marketo uses isn’t via status code, but via an internal error code our automated re-authentication systems do not work for Marketo with the Rest Snap Pack. I would highly suggest moving to that if it’s available to you, we don’t really have an option for retries beyond the scope of 401/403 where we force an OAuth refresh currently.