• Maximum number of repeats exceeded

:bullseye: What is your goal?

I keep receiving a “maximum number of repeats allowed” error along with a timeout message.

:thinking: What is the problem & what have you tried?

I currently have this connected to ArcGIS Field Maps so that it sends an email each time a layer is updated (when a task is completed). This workflow is only used by a department of four people and not on a daily basis, so there shouldn’t be a large number of points or updates triggering it.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Hi @Laura_Mott. Welcome to the community.

Where does the error happen? What’s it about?

This message is the consequence of the repetition of an unrecoverable error. You need to find the cause.

Look for a red triangle :red_triangle_pointed_up: on one of the modules in your scenario History. That’s the error.

@damato

Welcome to the Make community!

I suspect this error is related to Automatic retry of incomplete executions - Help Center, which automatically retries failing modules, and then halts the scenario if it doesn’t get resolved after a certain number of retries.

Handle errors so scenarios don’t stop

You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be ignored or retried after a short period. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw errors and get switched off.

Error directives can only be added to an error handler route

1. Right click a module and select “Add error handler”

2. Error handlers will appear

For more information on error handling, see:

Hope this helps! If you are still having trouble, please provide more details.

@samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!

1 Like

@damato

Looks like that module was waiting for data to come in but nothing happened. Did you run it manually? And was there an event on the other end that should have triggered it?

running manually seems fine, it’s supposed to trigger every time a specific layer in GIS is updated. But these errors have been coming nonstop all the sudden. It was working previously. Nothing changed on my end.