Geolocation cron update on archive

Inside the geolocation admin settings - Setup automatic updates of geolocation databases
It asks if " Update databases every" should be month or week (radio buttons).
With a message nearby:
The updater was last run on 2025-05-09.
It is scheduled to run during the next cron core:archive command execution.

Unfortunately the core:archive cron is set to run more often and according to the administrators at maxmind there are an excessive amount of fetch attempts, much more often than every month or week. It is confirmed by them that it was at the cron intervals.

I also saw a thread, re “You can also directly run the task using ./console scheduled-tasks:run "Piwik\Plugins\GeoIp2\GeoIP2AutoUpdater.update"” which would be suitable for our purposes if it works, but how would it be unhooked from the core:archive command? github matomo issue: matomo-org/matomo/issues/18353

Now the downloads from maxmind are curtailed by them and result like “Daily GeoIP database download limit reached” . I wonder if it is caught in some kind of loop continually trying to update that on every cron run. At our service level really we only want it once or twice a week at most. Thank you.