Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

The Zap is created adds a row to the PostgreSQL database whenever a row is added to Google Sheets. There are no errors. Whenever I toggle the Zap ON it later automatically toggles the Zap off when I refresh the page. There is nothing in task history and no errors. Can anyone point out if there is some error in the way I have created the Zap or is it something else?

 

Hi @zapier360 

I'm going to flag this post for the Zapier Community Team. They should have more insight on this and can escalate to the support team if needed.

Sit tight, and someone will contact you soon.

Hi @zapier360 If there’s nothing in the task history, then the most likely cause here is that the Zap is repeatedly hitting an error in the trigger step and therefore turning itself off. You wont see anything in the task history because the error is happening before any data can get to the Zap to trigger it.

We’ll need to take a closer look at the Zap’s logs to see why this is happening so I've escalated this to the Support team. Someone will be touch via email to help you with it as soon as possible.

Hey @zapier360 - We’re so glad that Chelsea got back to you. It was unfortunate timing that our field mapping was down at the moment in time you were experiencing the error. It was not you. Phew! 

Let us know if you have any further questions!

Terms & Conditions