The report always reflects the content that was available in your Archive workspace at the moment you generated it.
Our automatic detection of content is normally fast — posts that @mention your connected account are typically detected within minutes, while content found through tracked terms or creator sources can take a few hours to appear. For past periods, the dataset should already be stable. That said, it's still possible for a later export to include posts that weren't in an earlier one, and this doesn't indicate an issue with your report.
This can happen in a couple of scenarios:
When we improve our detection mechanisms internally: Sometimes, enhancements on our side allow Archive to identify posts that existed at the time but weren't captured previously. When this happens, older posts can appear retroactively in the workspace — and therefore in newer exports.
When content is added manually at a later date: Manually imported posts are stored based on their post date, not the date they were added, so they'll also appear in newer exports for that same historical period.
Filters applied at the time of export: Differences between exports can also come from the filters used. For example, if the initial CSV was filtered to show only Instagram posts, TikTok content from the same period wouldn't appear — even though it exists in your workspace. Any variation in platform filters, date filters, or label filters will naturally change what shows up in the export.
Different user timezones: Date filters are interpreted in each user's own timezone. If two teammates in different timezones export "the same" date range, the underlying start and end times differ — so posts published near the edges of the range can appear in one export and not the other. For consistent comparisons, have the same person generate both exports, or align on a shared timezone.
The Same Posts Can Show Different Numbers
Even when two exports contain the same posts, the engagement columns — likes, views, comments — can differ. Archive refreshes engagement on a schedule that adapts to how much traction a post is still getting (see Understanding Archive's Virality Score). An export generated on Monday and another on Thursday can show different numbers for the same post simply because a refresh ran in between.
One related behavior worth knowing: if a post is deleted or made private on the platform after Archive captured it, the post stays in your workspace and your exports — but its engagement numbers freeze at the last successful refresh and won't update again.