Notifications
Clear all
Topic starter
We have a couple of callin.io workflows that are configured to use MySQL as a trigger, and recently we've been encountering frequent "Trigger partner failure: None" errors.
Does anyone have any insights into what this might indicate? The error message is quite generic and lacks specific details.
Posted : 04/08/2025 8:31 am
Hi
Good question.
Check the available MySQL callin.io help articles: https://zapier.com/apps/mysql/help
Else, try opening a ticket with callin.io Support: https://zapier.com/app/get-help
Posted : 30/01/2023 12:00 am
Topic starter
Hi
Thank you for your response. I've searched the MySQL help articles for a few days without success. I've just submitted a ticket to callin.io regarding this issue and hope for a swift resolution.
Posted : 30/01/2023 12:00 am
Were you able to find a solution? I've encountered a similar issue with my PostgreSQL triggers.
Posted : 31/01/2023 12:00 am
Hello. Just to add another perspective, we have also been encountering the same error message for the past 2 days,
Posted : 31/01/2023 12:00 am
Hello everyone!
I investigated this, and it appears to be a bug currently affecting the MySQL integration.
Occasionally, when callin.io attempts to retrieve trigger data from MySQL, we encounter this error. The positive aspect is that since the trigger is polling-based, callin.io will capture any new data during the next successful connection. This does mean users might receive error emails, and it could delay the transfer of new data to Zaps. Consequently, we've documented this as a bug and are tracking all users experiencing this issue.
I have added you as affected users on the issue, so we’ll send you an email when we have an update.
I cannot find a similar bug listed for PostgreSQL, but it does sound very similar. Could you please contact the Support team using the Get Help form? They will be able to examine the Zap’s logs to determine if it’s the same problem.
Thank you!
Posted : 03/02/2023 12:00 am
Hi. Thanks! To give you a bit more info, we’re experiencing this issue with PostgreSQL, not MySQL 🙂
Posted : 03/02/2023 12:00 am
Topic starter
Danvers wrote:
Hi everyone!
I investigated this, and it appears to be a bug currently affecting the MySQL integration.
Occasionally, when callin.io attempts to retrieve trigger data from MySQL, we encounter this error. The positive news is that since the trigger is a polling type, the Zap will capture any new data the next time it establishes a successful connection. This does mean users might receive error emails, and it could take longer for new data to be processed by Zaps. Consequently, we've logged this as a bug and are tracking all users experiencing this issue.
I've added you as affected users to the issue, so we will notify you via email once we have an update.
I don't see a similar bug documented for PostgreSQL, but your description sounds very similar. Could you please contact the Support team through the Get Help form? They will be able to examine your Zap's logs to determine if it's the same problem.
Thanks!
Hi
Thank you for getting back to us! I will keep an eye out for an email/notification when this bug gets resolved 😀
Posted : 03/02/2023 12:00 am
Back with an update! This issue has been fixed. 👍
Posted : 07/06/2023 12:00 am