Make trigger retry if it fails

Hi, I am struggling with rather easy scenario - a watch WooCommerce orders module which pulls order data to G Sheets. The module works fine in general but it’s a huge pain when something is wrong with the connection. From time to time watch module gets strange error ( DataError (200), there are numerous topics on forums regarding this issue but no valid solutions ). So I want to just ignore this issue as it’s always fixed by itself in some time and retry later without stopping the scenario. But there’s no easy way to achieve this.

  1. “number of consecutive errors” from scenario settings does not work for me because it does not work for 1st module in scenario with DataError (according to help and my experience)
  2. “break” module works only partially - it leaves scenario active but it does not retry properly because when it fires I get following warning message " Trigger cannot be handled when processing an incomplete execution" and numerous warning emails.
  3. Sleep module as error handler won’t work as I can’t place another watch module after it (trigger must be the first module in the scenario)

So the only solutions I see is to either continue using break and get numerous warning emails or just use commit module instead with possibility of missing real errors. Both won’t provide retries, so I don’t like both.
I am quite surprised such an easy thing as “retry later if failed” can’t be achieved in Make.

blueprint.json (18.1 KB)

Having the same issue, but with Monday.com and Gravity Forms connectors. Getting the “Trigger cannot be handled when processing an incomplete execution” warning, but it always fixes itself. Really irritating.

1 Like

I’ve got some extra data. After enabling REST API logging for WC I see that there are no log entries for the attempts when I get DataError (200) on Make’s side. So probably this is some sort of connection error. Also this DataError (200) rarely appears once - either everything runs smooth or there are numerous errors during the day, although there still can be successful attempts in-between.

2 Likes

Did you find the origin of this error? I’m having a similar problem with my WooCommerce-connection(s)

Do you have a solution to this error? I have the same. Previously several times a day. Currently it has stopped working completely.