Since yesterday at 8:56pm EST, I am having an issue where the MySQL module will often result in a connect ETIMEDOUT error.
This will happen 1) when the scenario is run or 2) when the module is opened and the fields are being loaded.
When the scenario is run, it will fail with a connect ETIMEDOUT error maybe 50% of the time.
Similarly, when viewing the module, the fields will either load as usual, load slowly after several seconds (not normal), or completely fail with its very own ETIMEDOUT error.
Here is an example running the scenario with a simple query to the database using the MySQL module: Make MySQL Error.m4v - Google Drive
You will see the first attempt results in an ETIMEDOUT error, but the second try is instantly successful.
Nothing was changed on my end since the errors started last night at 8:56pm EST.
All Make IP addresses have been whitelisted for us1.make.com (and have been for months) with my host and have been working successfully in the past.
I first reached out to my host because I thought the issue was on their side, but the host has confirmed all is good: Screenshot 2024-10-22 at 10.51.40 AM.png - Google Drive
I have tried making a new connection to the database, and I still get the same errors.
I have tried a ticket with Make Support. Their initial repose was the error was caused by the scenario was returning no data. That is not true because the example is a simple query for ID = 65 which exists.
The second reply from Support was to whitelist the IP addresses, which I already addressed in the support ticket that the IP have been whitelisted for a while now.
This is a critical issue for me and has been causing Errors throughout the day in my most important scenarios. If anyone could be of assistance, I would greatly appreciate it.