The cloudways bot sent me this email yesterday but then when I tried to upgrade from Magento 2.3 to 2.4 with the $250 upgrade service I was informed that it is no longer supported. Here is the email:

"Hi there,

I, the CloudwaysBot, am here to inform you about an important message regarding your Cloudways server.

The version of Magento installed for your application is not up-to-date. There is a new version available. It is advisable to update to the latest version. If you prefer, you can request a managed application upgrade via the upgrade addon.

Feel free to get in touch with the support team via Live Chat for questions/comments.

Thank you,
CloudwaysBot"

I have auto updates enabled, and each time the site is broken until breeze cache is cleared. I notice breeze can be auto-cleared on posts and page updates, but is there no script I could add that would allow it to clear on plugin updates?

There have been several security issues recently that have required sites to be updated immediately. Several plugins have had zero day vulnerabilities that require immediate attention. I have too many sites to update manually as quickly as the plugin authors would like.

Enabling auto-updates on plugins is a great solution, but Breeze cache is the only thing stopping it from working, because each plugin update requires me to clear the cache or my users see a broken layout.

Even if updating plugins manually, why should we have to manually clear the cache also?

I have this database with a table that has 2 generated (virtual) columns. I exported my database using your built-in database manager. Then I imported the SQL using the same tool. Unfortunately, there's an error, and it said that values are not accepted for virtual columns. Upon checking this bug reports: (1) https://bugs.mysql.com/bug.php?id=79148 , it says there that the bug is already fix in higher version of MySQL.

Please update the available MySQL version, please.

What I did just to get around with the bug was to manually delete the exported virtual columns with their values in the exported SQL file.

And it's super, super hassle to manually remove those part.

Cloudways is still running Git 2.1.4 released on 18-Dec-2014. A handful of really neat features have been added to Git since then. One new feature that would be very helpful to have on Cloudways servers is the updateInstead option for the receive.denyCurrentBranch config added in Git 2.3, which allows pushing directly to the server even if the branch is checked out on the server. This would eliminate the need to set up a repository on an intermediary server. Users could just add their Cloudways server as a remote in their local git repository and push directly from there to the server.

I suggest to update Drupal 8 one click install to the Latest and recommended version. As of the date of this idea post, the recommended version is 8.3.7
Due to a security fix, it is recommended to update

Alternatively, users can use Drush as it is included in the Cloudways Stack, as follows:

1. Put the site in Maintenance mode via Drush : $ drush sset system.maintenance_mode TRUE

2. Clear cache via Drush : $ drush cache-rebuild

3. Run the update via Drush : $ drush pm-update drupal

4. Take the site out of Maintenance mode via Drush : $ drush sset system.maintenance_mode FALSE

If you run into the error "Unable to load class \Drush\VersionControl\Backup" Move the folder outside of the drupal root and try updating again OR call cloudways tech support to assist with security update.