Hi ​@Hugaluga 

Help us have more info by posting screenshots showing:

• the encountered error in the Zap Run
• how your Zap steps are outlined and configured in EDIT mode with the field mappings visible

Is the field mapping relevant? From what I’ve read a handled error should not send a notification - and I believe it didn’t use to.

I did include some screenshots (including one of the email), but I am not sure they will provide any important context.

​@Hugaluga 

You may be getting those email error notifications because the Zap step encountered an error for required fields and could not be attempted, which is different from a Zap step with required fields having values and able to attempt the action step but the action returns an error.

• One is more a Zap step config issue, which could/should be prevented by using Filter steps to check the mapped variable in a required field has a value.
  • Filter: https://zapier.com/apps/filter/help
• One is a Zap step response issue.
  • e.g. required field had a value, but the value was invalid.

I think you’re likely right. I didn’t realize the system handled an absence of data differently than a failed lookup. 

These lookups are not key to my process and I would like the zap to proceed either way - so a filter isn’t ideal… I’ll probably have to use paths instead. 

The good new is that I probably don’t even need error handlers because of this setting on lookup tables:

I think the Post step will just sent empty data which is fine. 

It would be really really really useful if lookup tables had a third option to mark successful if lookup value is missing. All of this extra pathing is exhausting when I have 50 similar zaps to maintain. If you have the ability to pass along that suggestion, I’d appreciate it.

And of course, I appreciate your help. Thank you!
 

For anyone curious, this is the alternative solution using pathing compared to my error handler solution:

​@Hugaluga 

I do not work for Zapier, so best to submit feedback and feature requests officially thru a ticket with Zapier Support to be logged: https://zapier.com/app/get-help

Paths/Filters are a better way to handle missing data for Zap step input fields.

Also, if you have that many similarly configured Zaps, then you probably want to consider a more dynamic Zap design.

Sub-Zaps for reusable steps: https://help.zapier.com/hc/en-us/articles/8496308527629-Build-reusable-Sub-Zaps

Webhooks can be used to chain Zaps together for reusable Zap steps:

• 1:1
• 1:MANY
• MANY:1

Lookup Tables are another way to make Zaps dynamic by creating a log/queue to use across Zaps.

​@Troy Tessalone I appreciate your recommendation to use Sub Zaps… it’s a bit of work upfront to switch everything over, but I’m hopeful that this will make maintenance much more straightforward. 

Thanks again for your help!