Support

Kindly note that Joomla! Scheduled Tasks are managed and executed by Joomla! itself. We have no say on that code. You probably need to read https://www.akeeba.com/documentation/akeeba-backup-joomla/automating-your-backup.html#joomla-tasks-danger-ahead to understand the caveats of using Joomla! Scheduled Tasks.

Instead of using scheduled tasks you can just use the standard CLI backup command, see https://www.akeeba.com/documentation/akeeba-backup-joomla/automating-your-backup.html#native-cron-script Since you will be scheduling this with your server's CRON it will always run on the specific time you have configured.

1. Scheduled Tasks and their rescheduling time is handled by Joomla. We have no say on that code. Therefore, we cannot do anything about it.

Here's the thing. Joomla Scheduled Tasks DO NOT guarantee that a task will be executed at a specific point in time. It's contrary to its concept. It only guarantees that a task will eventually run sometime after the predefined execution time, if and only if there is a functional trigger mechanism for Joomla Scheduled Tasks (CLI CRON, web URL, lazy scheduling) which dutifully triggers Joomla Scheduled Tasks' evaluation often enough for all scheduled tasks to execute correctly. CRON jobs always run at the time you specified.

Joomla Scheduled Tasks DO NOT guarantee that rescheduling will result in a predictable date and time unless you use the CRON Expression scheduling method. Using settings like Daily provides zero guarantees. For example, Daily only means that the task will be rescheduled to run 24 hours after it's finished, whenever that is. Since tasks have a non-zero execution time the rescheduling will make them time-shift on every execution. CRON jobs are always rescheduled using the CRON job settings.

Therefore, if you want to have guaranteed task execution and rescheduling time you must use CLI CRON jobs with your host. It's a matter of using the right tool for your use case.

Let me put it this way. CLI CRON jobs are cars. Joomla! Scheduled Tasks are busses. When you use your car you can always get in it at the same time every day, and arrive to your destination at around the same time. If there's a traffic issue along the way you can reroute instead of being stuck in traffic forever. It's predictable to a very high degree. When you take the bus it will eventually come, assuming there's no strike or the badly maintained bus broke down again, but it won't be exactly the same time every day. It will eventually take you to your destination, maybe, unless it breaks down, or there's a strike midway through your journey, or there are too many people getting on and off the bus, or there is a traffic issue within its predefined and inflexible route. If you want to always leave your house on time and be on time, you use the car, not the bus. Expecting the bus to always be on time and predictable is asking for too much.

2. Obsolete records are removed per backup profile when their number exceeds the configured value for that setting. That's the only control you have.

Day-based backups quotas control when your backups archives will be removed, either from your web server or your remote storage depending on the quota type. They do not control removal of obsolete records. They may cause a record to become obsolete, but they won't remove it, and this is by design.

The maximum backup age setting in the backup notification quick icon is only used to determine when you have not taken a backup in a while, based on the backup records in your database. It does not modify or remove backup records.