I also experienced the DB growth (thought it was because of another error first).

It seems that it catched the new message i introduced here (same for me currently) #7305

Is there a bug i dont see from my PR?

//Update i got it now shrinked again with the force parameter

Purging temporary archives: skipped (no authorization)

is shown if browser archiving is disabled and $_GET['trigger'] != 'archivephp'.

When running in the console $_GET['trigger'] is most probably empty, so if Piwik is using cron archiving you can't purge temporary archives…

Is that the intended behavior? Here is what the comment says:

we only delete archives if we are able to process them, otherwise, the browser might process reports when &segment= is specified (or custom date range) and would below, delete temporary archives that the browser is not able to process until next cron run (which could be more than 1 hour away)

Note the --force option just forces to run scheduled tasks (i.e. it applies only to the task scheduler).

Then each task has its own rules, I'm not sure it's easy to pass the concept of "--force" inside the actual logic.

@mattab No longer relevant at least for archive purging since there is a dedicated command for it now. Since --force does force running scheduled tasks, I think this issue can be closed.