Hi @PMalmont,

There are a few settings, including IP address instances that need to be taken into account when creating a new MySQL connection. Please review the article below for more details: How to get started with MySQL

Given that this is a new app, you will want to try using "connect a new account" instead of reconnect.

Please try this out and let me know if you are able to establish the new connection.

hi.

No luck.  Adding screenshots of what I’m doing to see if that helps you help me.

Hi there, @PMalmont 

Thanks so much for sharing those helpful screenshots and for giving Ken’s suggestion a try. I did some digging and came across a bug report that matches what you’re running into here. So I’ve added you to the list of folks being impacted by this issue which will help to increase the issue’s priority ranking. Although we’re unable to give any sort of estimate as to when it’ll be resolved by you’ll definitely get an email notification as soon as it is!

The only workaround I could find mentioned on the bug report was that connections to the legacy version or the MySQL app worked fine, so it may be worth switching back to the older version of the MySQL app for the moment:

Thanks in advance for your patience in the meantime, I do hope the team will be able to get this sorted soon. We’ll be in touch with any updates on the status of the bug! 

I'm having the exact same issues after upgrading to the new MySQL app. Now I'm trying to switch back to the legacy app, but getting time-out errors when I connect to the DB.  Hopefully I will be able to succesfully switch back to the legacy app.

Hi @RobinK1978,

Thanks for reporting this to us.

I have added you to the open bug report. While we can’t provide an ETA for the bug’s fix. We will keep you updated via email once it is.

I appreciate your patience and understanding.

Hi 

just reporting same issue here

will use legacy then.

thanks

Personally I was not able to use the legacy anymore either. I just switched off my zaps for now, because I was not able to get the zaps working again with MySQL.

oh, no, that’s really annoying !

Hi ​@mikaelmm,

I’m really sorry to hear about the inconvenience this bug has caused you. I have added you to the open bug report. We will keep you in the loop via email once the bug has been fixed.

I appreciate your patience and understanding.

Hey folks,

Circling back in here to share the bug has been resolved! 

There’s nothing you need to change in your Zap to get things working but your Zap(s) will need to be running the latest version of the MySQL app to take advantage of this fix. 

I’ll be closing out this topic now that the bug has been fixed but if you continue to experience this issue please do reach back out to the Community or contact Support directly to let us know. In the meantime, happy Zapping!