About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials Zapier University 101

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

How Do I...? Troubleshooting Popular Apps Q&A 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

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

Interest Areas User Groups

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

Zapier University 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.

Best answer

MySQL error: Trigger partner failure: None

  • 30 January 2023
  • 7 replies
  • 52 views
B

We have a couple of Zaps that are set up to use MySQL as a trigger, and lately we have been getting a lot of this error message: “Trigger partner failure: None”

 

If anyone has any ideas on what this is signifying? The error message is pretty bland and doesn’t provide any details.

icon

Best answer by Danvers 2 February 2023, 23:37

View original

7 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @BudgetCoinz 

Good question.

Check the available MySQL Zap help articles: https://zapier.com/apps/mysql/help

Else, try opening a ticket with Zapier Support: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Certified Zapier Expert (Premier Tier) | #1 Zapier Community Contributor
B

 

Hi ​​​@Troy Tessalone 

Thank you for your response, I was not able to find anything in the MySQL help articles, I have been for a few days. I just submitted a ticket to zapier about this issue though, hopefuly they can response quickly so we can get this figured out. 

 

 

K

Did you get an answer? I’ve experienced the same with my PostgreSQL triggers.

PDFMonkey
Userlevel 2
Badge

Hi there. Just to add another voice as we’ve been getting the same error message for 2 days,

Danvers
Rank
Userlevel 7
Badge +12

Hi everyone!

I took a look into this and it seems to be a bug that the MySQL integration is hitting right now. 

Sometimes when Zapier is reaching out to MySQL for trigger data, we’re getting that error.  The good news is that as the trigger is a polling trigger, the Zap will pick up any new data the next time it gets a successful connection. This does mean that users will get error message emails and that it may take longer for new data to get passed to Zaps, which is why we’ve recorded it as a bug and are logging all users that are running into the issue. 

@BudgetCoinz and @PDFMonkey, I’ve added you as affected users on the issue, so we’ll send you an email when we we have an update. 

@kevinoyen I can’t see a similar bug listed for PostgreSQL, but it does sound very similar. Please could you reach out to the Support team using the Get Help form as they will be able to take a look at the Zap’s logs to see if it’s the same issue. 

Thanks!

PDFMonkey
Userlevel 2
Badge

Hi @Danvers. Thanks! To give you a bit more info, we’re experiencing this issue with PostgreSQL, not MySQL 🙂

B

Hi everyone!

I took a look into this and it seems to be a bug that the MySQL integration is hitting right now. 

Sometimes when Zapier is reaching out to MySQL for trigger data, we’re getting that error.  The good news is that as the trigger is a polling trigger, the Zap will pick up any new data the next time it gets a successful connection. This does mean that users will get error message emails and that it may take longer for new data to get passed to Zaps, which is why we’ve recorded it as a bug and are logging all users that are running into the issue. 

@BudgetCoinz and @PDFMonkey, I’ve added you as affected users on the issue, so we’ll send you an email when we we have an update. 

@kevinoyen I can’t see a similar bug listed for PostgreSQL, but it does sound very similar. Please could you reach out to the Support team using the Get Help form as they will be able to take a look at the Zap’s logs to see if it’s the same issue. 

Thanks!

Hi @Danvers 

Thank you for getting back to us! I will keep an eye out for en email/notification when this bug gets resoleved 😀

Reply


Terms & Conditions