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.

Most of my zaps are returning: 

Trigger partner failure: read_hook() missing 1 required positional argument: 'cleaned'

I’ve received 80 error emails over the last 45 minutes, even though none of these zaps have been triggered.

This error came up for me too today when I tried to create a new Zap using a Squarespace form

Hey hi!

Same issue

I just received a zapier alert about this issue. They are working on it 

Check the status page: https://status.zapier.com/

Thanks!,

I got the Zapier alert message right after I filed the question. They updated status.at 10:26 PST, I started getting the error messages about 9:39. ;)

Same issue

I just received a zapier alert about this issue. They are working on it 

Check the status page: https://status.zapier.com/

 

Hey all! I wanted to pop in and confirm that  @alejandromedina is correct! SO fast. 🔥 This is a known bug impacting the Zapier Manager and ZapierMail apps and the team is working on a fix. We’ll keep ya’ll posted with updates but status.zapier.com is a good place to monitor as well. 

Just a heads up @alejandromedina to keep everything consolidated, I’m closing your other thread and moving everything here as the primary for ya’ll to watch. 

Thanks so much for being so quick to keep the community updated! 

Hi everyone!

Just to confirm, this issue was resolved on December 16 so you should no longer be seeing this error. If you are, please get in touch with the Support Team using the Get Help form so they can look into it ASAP for you. If you’d like to see the full history of this issue, you can find it on Zapier Status incident page for this event.

Thanks!

Terms & Conditions