This is a follow-up to #15831.

Since upgrading to 3.13.5, I was able to get my bloated archive tables back to their proper size by running ./console core:purge-old-archive-data all.

However, since then, the tables began to grow in size again.

Things are much better since 3.13.5. I was able to shrink the tables again by running the purge-old-archive-data command again. My largest archive blog table then shrank from 50,456 rows and 236 MiB back to 9,910 rows and 7.0 MiB. So I now have a way to solve the problem of the bloated tables (whereas, before 3.13.5, I had no way to shrink those tables).

However, they are surely not supposed to grow to the point that they need pruning with a manual command. The table referred to above is for January 2020, to which no new data is added, so I'd expect that archive table to remain the same size.

It may well be that the problem is actually my end. Having read the documentation, I'm running a maintenance command once every 10 minutes:

/usr/bin/php ~/public_html/console core:archive --url=https{domain} >> {log-file}

Is there another command that, when Matomo is behaving correctly, needs running on schedule to keep things running smoothly? (I realise I could run purge-old-archive-data with cron, but is it correct behaviour for me to need to do so?)

Or are the tables still bloating when they shouldn't be?