Bug No 1: MySQL backup keeps showing a deleted backup that has auto-deleted by cron job.

See the below list of DB Backup

This is the list of DB Backups generated by Cron job ➔ DB Backup tasks.

The interesting fact is that none of the above backups exists on the server. Because they have been auto-deleted by cron-job, as we did NOT CHECKED the option to Keep local backup

If you try to download it. It will navigate to the below error page.

Bug No 2: Cron job does not honor the request of "Keep local Backup" for the existing cron jobs (that have been created in the past).

After facing the above bug, we checked the option Keep local backup. So, we should not encounter the fictitious backup list. As it will be unsafe if we do not get backup that we are seeing.

However, the cron job still keeps deleting the backup files that it generates even though we checked to *Keep local backup**.

Bug No 3: The option to control the local backup does not show while creating the new cron job

However, the option to control the local backup appears while editing the existing cron job. But it remains hidden while creating the new cron job.

I've checked the existence of these bugs on the aaPanel on CentOS 7 & 8, both have the same issues.

I tried to explain these bugs as easily as I can. Still, let me know if something missing or needs more clarity. Thank you.