Disable automatic zap turn of if multiple errors occur

Hi @MAV 

Suggestion: Best way to correct for this would be to put in a Filter in the Zap to prevent the error.

Hi @Troy Tessalone where and how shoud I put this filter in ZAP, maybe you could give me an example?

@MAV 

Best to put Filter steps as early in the Zap as possible to save on Tasks.

Depends on what criteria you are trying to prevent errors against.

Would need more context about what is causing the errors in your triggered Zap Runs: https://zapier.com/app/history/

@Troy Tessalone  here is the printscreen for the error in Zap runs:

Hi @MAV 

It’s unclear what Jira Cloud action or search you are using for Step 2 in the Zap.

Can you please clarify?

The error indicates the JQL query is malformed: https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Hi @MAV!

As a backup: you can also use the Zapier Manager as the trigger in a Zap, to catch Zaps that turn off, then again Zapier Manager as the action, to turn it back on. 

@Troy Tessalone 

I will explain all three steps for this Zap:

1. In the first the Zap find a Trello card with some activity and takes this card name.
2. In the second step Zap looks for this Trello card’s name in Jira Issue list, and as we can see from error Zap can not find this issue (as I mentioned that there are internal cards in Trello as well, which are not associated with Jira)
3. In the third step Jira issue with the same name as Trello card which was determined in the first step is updated.

Hi @MAV 

Try adding a Filter step between steps 2 and 3 as you’ve listed.

In Step 2 there should be a field like the one below in the screenshot.

Make sure to set the value to “True”.

This will allow the Zap to continue even if nothing is found in Step 2.

Then in the new Filter step add a condition to only continue if there is a Jira Issue ID returned (aka exists).

This will allow the Zap to fail gracefully instead of resulting in errors.