Skip to main content

Hello! Looking for help with nested error handling to see if I’m running in to a common bug or doing something wrong.

Here's the setup: we're searching for a deal in HubSpot, then sending an email if it's found. If the deal isn't found, we use a delay action to try again later, so the Zap doesn't fail immediately.

As you can see in the attached image, I've set up error handling for the steps. When the first error occurs, the Zap correctly moves down the error path as expected. However, after that, once it goes through the second error handling, it successfully found the deal, but then skips the Microsoft Outlook action that should create an event.

The logic seems to be working fine up until that point, but I'm not sure why the Outlook action is being bypassed after the second error handling. Any ideas on what could be causing this behavior?

Thanks in advance for the help!

 

 

Hi @Hawkins300 

Looks like you are using an outdated version of the Outlook Zap app, so make sure to update that step.

Help: https://help.zapier.com/hc/en-us/articles/18755649454989-Update-to-the-latest-app-version-in-Zaps

 

Check your Zap Runs history to see the DATA IN/OUT for each step to help you troubleshoot:

https://zapier.com/app/history/

 

Try using Paths instead of OR with the Error Handler.

Here’s why…

Configure the HubSpot Deal step to always continue if no Deal is found.

When a Deal is not found, if the Zap action step is configured correctly, then that is not an “error”.

The request was valid to HubSpot, the response was valid from HubSpot, just no Deal matched the search criteria.

You can use Paths to process for the cases where a Deal is found VS a Deal is not found.

 

Help links for using Error Handlers: https://help.zapier.com/hc/en-us/articles/22495436062605-Set-up-custom-error-handling

 

If you suspect a bug with the error handling, you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

appreciate the response but doesn’t seem like any of these truly fix it. With that said, i’ll try using paths instead of error handling.

I have updated the outlook version and the error persist. It should be noted that the flow has worked fine if a deal is found in the first find deal step.

I can edit it to use paths instead of error handling but that seems to prove that this is a bug. The find deal function is indeed throwing off an error when no deal is found. You can see that in my screenshot towards the top, where it halted the step because no deal was found and then it proceeded correctly down the error path as expected.  

@Hawkins300 

In the HubSpot Find Deal step, set the field “Should this step be considered a success if no search results are found?” =  YES

Then you can have 2 paths:

  • Path 1: Found = False
  • Path 2: Found = True

 

Reply


Terms & Conditions