I want to include the resume error handler in a scenario that finds data through an email address.
The scenario receives an Gmail with payment information and then processes the information to send a receipt. I am using Airtable to the client details, so I’m searching a “Member” table with the email address from the Gmail.
When the “Member” table says it doesn’t have that email address, there is a linked table (partner) that the email address will likely be in, along with the sender name.
What I want to do with the resume error handler is similar to this image from another answer by @DavidGurr_Make
I have concerns about the placement of that aggregator (or would an iterator work better!!?)
If I run the modules independently they work fine, and I can populate the resume part effectively. I just can’t figure out how to get the handler to activate when Airtable doesn’t find a match to the email address provided by Gmail. I don’t even know if I have the handler in the right spot!
Any help, comments, alternatives are gratefully sought before I pull my hair out!
This is because a “Search Records” module will likely never throw an error (even if not found). It will just return 0 records/results.
If you can compare your scenario closely to the examples you’ve linked, they are using a “Create” module – which will throw an error if the item already exists.
Replace your first “Search Records” module with a create module from the same Airtable app.
Thanks @samliew, I gave that a try at your suggestion, and it doesn’t really make sense for my given usage of the scenario. For now I already have it created in a way that works, so this idea was/is experimental.
Create at the first search module means that every legit email throws an error on every ‘found’ email, and creates a new entry in the wrong table, which is not what is needed. I can see a way to avoid that, but it means adding more lookup fields in the original table which I’d rather not do at this point.
Your point about “create vs search” is well taken, and I’ll keep that in mind for other uses of resume.
For now, I elected to expand the search criteria for that first search module and that is working fine.
Hi all,
Not sure if my issue is exactly the one the topic is about, but
one of my steps is Fluwlu and it has a limit per second API call. If exceeded, the entire flow stops and turns off. How can I tell the flow to ignore the error and continue with remaining steps even if error?
