I am pulling in a table from a MySql Database that has millions of rows. All other tables are pulled n correctly, no worries. This table gets to about 5million rows and then just fails saying Timeout Experienced (eventhough everything is up and running).
As far as MySQL timeout errors go, this addresses one end. There can be a timeout on the server as well as a timeout on the client. In this case, it seems that it was a timeout on the server end, which when addressed resolved the issue.
However, I ran into a similar error message, with my data refresh failing after 11 minutes or so. My server timeout was set to indefinite, so the problem wasn't on the server. It turns out by default the CommandTimeout on the MySQL.Database() function in Power Query M is set to 10 minutes. I was trying to download 3 million rows, and it was taking more than 10 minutes, and so it would fail.
The option to set the CommandTimeout is as an optional record in the third parameter of the MySQL.Database() function.