@tsteur found the fix. The cause is since we call
CoreAdminHome.archiveReports now instead of
API.get, the dependent archive isn't implicitly created. Adding an archiver for VisitFrequency fixes this, though I'm not sure if we want to maintain the old behavior.
sounds good for now 👍 . I don't think it affects any other
*.get methods so should be fine IMO
@tsteur will also add an update to automatically invalidate, unless you think that's a bad idea.
I'm assuming this would mean we rearchive all the data from the last few months not just this report?
I think we can just re-archive visitfrequency from start of matomo 4 upgrade to now. We just need to trigger the VisitFrequency archiver which will process dependent archives. So we shouldn't need to do every archive.
👍 sounds good
added the update file