Error Handling stops proper iteration

[tealord]

What are you trying to achieve?

Hi erveryone,

I hope you can help me with my problem. I searched the docs and the community but didn’t find the answer.

Here is my setup:

1. I make an Hubspot API call to get a list of user IDs.
2. I iterate them to update the contacts

Now to the problem:

If I get an invalid ID of cause the module “Hubspot update a contact” throws an error. I just want to ignore the error and move on with the next element from “Iterator”.

So I tried error handling “Resume” which resultet in the behavier that I do not revieve the next data from Iterator. (Also tried “Ignore” with no success)

In the attached screenshot you can see that “Operation 10” hat a Contact ID like every operation before but only that this one throws an error. From there on every following Operation does not have an INPUT but an HANDLED ERROR.

Can you help me understanding whats going on and how to fix the issue so the following Operations will get the ongoing Inputs from Iterator again?

Steps taken so far

See text above

Screenshots: scenario setup, module configuration, errors

[Barbara2]

Hello

I am new to Make myself, working through the Academy. Currently at course “Error Handling” in the Make Academy. Have you done the curse on error handling?

In unit 1 (Errors Overview) it says

https://academy.make.com/courses/take/IntermediateC05/multimedia/50258139-unit-1-errors-overview

Have you enabled incomplete executions? It might help since then your mapping errors will become warning and won’t stop the scenario.

[Barbara2]

I created a simplified scenario where an iterator iterates through a list and a 404 error occurs with the second bundle (but first, third and fourth bundle are successful).

When you change the settings as described in my comment above, the 404 error will turn into a warning and an incomplete execution, but will not block the third and fourth bundle.

Check out the blueprint here:
iterator404ErrorBlueprint.json (10.7 KB)

[tealord]

I found the error. It was in the data and had nothing to do with the error handling or the iterator. Thank you very much @Barbara2 for your effort and sorry for the noise.