Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I’m having a hard time testing the `z.request()` in combination with the `skipThrowForStatus: true` setting.

My understanding from running on the Zapier platform is, that it does not throw an Error but returns the response instead.

However running with `zapier test` the following code with the node platform (current zapier-platform-core@12.0.3):

    const results = await appTester(async (z, bundle) => {
      for (let step = 0; step < 100; step++) {
        console.log(step)
        /** @type {ZapierZRequestResponse} */
        try {
          const response = await z.request({
            url: `${bundle.authData.server}/api/endpoint/`,
            headers: {Authorization: `Token ${bundle.authData.api_token}`},
            skipThrowForStatus: true,
          })
        } catch (e) {
          const ee = e
        }
      }
      return null
    }, bundle)

it always throws on a 4xx. But the reason to test here is to actually provoke the error and then handle it for which the HTTP response unfiltered is required and for which I thought skipThrowForStatus: true was appropriate.

Is there a way to make use of that request option property within tests?

Found it myself: z.request() is delegating to the http middleware defined per the test-app in AppTester and that one was not looking into that attribute and then always throwing (so our own code did the throw).

Fix is to handle the case on looking into response.request.skipThrowForStatus there.

/* HTTP Middleware */
const handleHTTPError = (response, z) => {
  if (response.request.skipThrowForStatus) {
    return response
  }
  // ... standard error handling code ...
}

References:

Nice work figuring this one out, @toktok !

You’re not the only person to get confused about this. I’ll drop one more link here for anybody else who finds this, and that’s for the CLI changelog at version 10, where we introduced a change to how the middleware was/wasn’t called and this change could break existing error-handling code if folks weren’t careful.

Definitely let us know if you have any more questions!

Sure, and thanks @shalgrim. Btw., this is why I put the core version in, and Yes! having the change-log entry is a great addition, too.

And to add up to it, this is also another context reference I found useful yesterday, editing it in now:

Together you and I will re-document everything! 😁 

Terms & Conditions