As I write this, I'm 99.99% certain the answer is no, but just for fun, I'll ask it anyways.
I've built a set of zaps for a client, to allow them to run a variable number of checklists in Process Street, based on the variable number of stores they manage (roughly 1100). The first zap runs based on a schedule, grabs the variable number of stores from a Google Sheet as a single concatenated value, pastes them into another sheet as individuals rows, which triggers the second zap.
Because of this, roughly 1100 rows are created each time this runs (once a month). The second zap is then triggered by the new row created, which then takes the data, confirms it via a lookup back to the Google Sheet, and then runs a checklist in Process Street.
This is a way to essentially do a loop, on a schedule, for a variable amount of entries containing variable data, using a zap. I'm gonna be making some content around this later.
However, the sort of minor issue is that the sheer number of rows created (and therefore zaps triggered), hits the 100 task flood protection limit (https://zapier.com/help/troubleshoot/behavior/rate-limits-and-throttling-in-zapier), and is then held by Zapier until I approve them.
This is fine if I'm able to jump right in and approve them, but not so if I'm out and about. Also, this makes me responsible to approve this automation every time from now until forever.
Is there a way to turn off the flood protection for this one zap? I think not. Alternatively, I could probably come up with a creative way to work around it, but why not propose this challenge to the community? Enjoy! :P
Best answer by jesse
View original
