As you're probably starting to realize, automation is amazing.
BUT… It's not perfect.
And when you're starting out, you'll inevitably run into bugs - just like we did. Which can be frustrating if you don't know how to deal with them!
Let's dive into it.
To fix this issue, try these 3 steps:
Step 1: Go to your Zap and make sure it's turned on:
Step 2: If it is turned on, click on the Zap to go into the editor and retest both the trigger and the action steps of your Zap:
Step 3: Still not working?
If none of these help, check out these recommendations by Zapier
Sometimes you create a Zap, you turn it on, and then you close your browser thinking you're done.
But when you come back, you realize your Zap hasn't been running.
"What the heck!?"
This problem is typically created by one of these 3 reasons:
To solve problem #1, check the task history of your Zap so you can get more details on the error.
To solve problem #2 and #3, you'll have to upgrade your plan (or wait until the next billing period so you get more tasks!).
Dealing with different time formats and time zones can be confusing - especially at first!
And sometimes the apps you're working with won't display a date or they will but in an incorrect format.
To fix this:
You can learn more about date formats here.
Sometimes your Zap might seem like it's running perfectly but the action is still not being completed.
The problem? It isn't sending any data. This is a common bug when you're building Zaps involving media files.
To fix that, go to your Zap editor and make sure your fields are properly mapped
Still not working? Go to your Zap History and check if it's pulling empty values
If you see a bunch of curly brackets in your Zap task history, it means your Zap is indeed pulling empty values. Check out this resource to learn how to fix this issue.
Lastly, the infamous "loop."
A "loop" is when one of your Zaps run over and over again from a single trigger event - until they suck up all your tasks!
This typically happens when you have two Zaps that trigger each other. For example:
Zap 1: When a new contact is added to Salesforce, create a new contact in Google Contacts.
Zap 2: When a new contact is added to Google Contacts, create a new contact in Salesforce.
Or when the trigger and the action of a Zap are the same:
"Looping" Zap: When a new contact is added to Google Contacts, create a new contact in Google Contacts.
This ends up unintentionally firing off Zaps and eating up your tasks.
When this happens, you need to update a field in both of your "looping" Zaps and then create a filter. You can find more detailed instructions here.
And that's it!
Every week, you’ll receive a no-code automation idea you can implement in 10 minutes & save yourself 10+ hours a week.