Not really a question, rather we wanted to share our experience in case it will help someone else.
We were having problems with a task that runs continuously in our Qlik Sense Enterprise (May 2024) instance that updates and app from some views in a our MySQL instance (8.4).
We were running this setup for a year or so with MySQL 5.8 across multiple versions of Qlik Sense and the task would fail from time to time but we were not concerned because we know that this usage for near real-time monitoring is not exactly a recommended use case for Qlik Sense. Besides, automated retry would facilitate recovery and it would it would only happen a few times a week at most.
Once we upgraded to MySQL 8.4 though the failures started happening 4-8 times a day. Now we know that 8.4 is not technically supported by the connector but our testing did not reveal an issue so we went for it to address security audit requirements.
The server resource were not being taxed and we weren't running up against the concurrent task limit or anything. We combed over the logs and found some pretty non-descriptive errors so rather than setting up more intrusive logging we though to replace the MySQL connector with an ODBC connector using the "MySQL ODBC 9.1 Unicode Driver" instead, just see if there is a change in behavior.
Sure enough there have been no more failures since this change. It is quite a relief.
Now I am not saying the way we got to were we are is good or recommended but... if you happen to find yourself in a similar scenario, perhaps our experience will give you some ideas on how to address your issue.
