403 error while using Session Auth

I have the same problem with handling a 403.

I have added (in Zapier ui with Session auth) the following:

return z.request(options).then((response)=> {
  if (response.status === 403) {
    throw new z.error.RefreshAuthError();
  }
    response.throwForStatus();
    const results = response.json;

    // You can do any parsing you need for results here before returning them

    return results;
  });

However with a zap running (after the first token has expired), I get the error: 

Cannot read property 'RefreshAuthError' of undefined

Can someone help me with this problem?

Hey @Abdur and @HielkeRijpstra!
 

@Abdur, it looks like you also reached out to our Support team and had set up your integration correctly to refresh the token. So it looks like you might be all set here. :)
 

@HielkeRijpstra, I did some digging and it looks like similar issues have been discussed in the following threads:

Hopefully the information in those threads will be helpful in finding a solution. If not, please do reach out to our Support team and they’ll be happy to help further on this! :)

Hi Sam,

Thanks for the links to other solutions. However if I try these, i stil get the Cannot read property 'RefreshAuthError' of undefined.

This is my handling of the reponse. 

z.request.skipThrowForStatus = true; // deal with 403 our selves

  return z.request(options).then((response) => {
  if (response.status === 403) {
    throw new z.errors.RefreshAuthError();
  }  // when 403 then get new bearer token
  response.throwForStatus();
  return response.json;
});

I can see that it catches the 403, but the bearer token is not refreshed:
What happened (You are seeing this because you are an admin):
  Starting POST request to https://heimdall.bouw7.nl/project
  Received 403 code from https://heimdall.bouw7.nl/project after 526ms
  Receive

I am using the UI of zapier, but not sure how i can fix this. Can you help me?

@SamB Could you help me out? 

I am struggling with the authentication as mentioned in my previous question.

Hey @HielkeRijpstra!

I’m so sorry you’re still running into some trouble on this. :( Hmm, it looks as though the code you’re using is a match for the code that was mentioned as having worked in this related thread:

• Handle 403 Error as 401 (auto refresh acess token) [Oauth 2 , Platform UI ]

I’m not too sure why it’s not working in your case. As I’m not able to dig into the set up or logs for your integration, I’d really recommend contacting our Support Team for further assistance via the Get Help form. They’ll be better placed to advise on any changes that you may need to make to the setup of your integration.