Fix "Not found" errors in Zaps

Last updated:

Sometimes you might get an error that says a record is not found. You’ll see these errors either after testing an action step, or if you’ve already turned your Zap on, in your Zap History. This can happen for a few different reasons.

1. Check if the record exists in your app

If you’re trying to update a record that exists in another app, but you’re getting the “not found” error in the action step, it could be that the record you’re trying to find or update does not exist.


If you’re trying to update a contact in Salesforce, make sure that the contact you’re trying to update already exists in Salesforce.

2. Check your custom value or search criteria

3. Add a delay step

If your Zap is creating a new record in one step and then later updating or referencing that same record in a later step, you might need to add a delay step in order to give the app time to create that new record.


For example, if you have an action that creates a new card in Trello from some data and a later action that moves that same Trello card to a new column, you may need to add a delay step in between to give Trello time to make the card.

Need More Help?

Contact Support

Tell us about your problem, and we’ll find you a solution or you can email support.
Get Help

Hire an Expert

We have a directory of professionals across the globe who are ready to help.
Find a Zapier Expert

Zapier Community

Connect with other Zapier users and industry professionals to get help crafting the perfect workflow.
Check out the community

Zapier University

Video courses designed to help you become a better Zapier user, whether you’re a beginner or more experienced.
View courses