While it runs, status, pause, resume and extend
A hashtag report shows a watch bar with three states (collecting daily until a date, paused, finished), pausing loses nothing because resuming picks up what was published meanwhile, and the end date always outranks the switch.
A link-based Instant Report is finished the moment its links are read. A Hashtag Report keeps going, and the panel at the top of its Influencers tab is where you control that.
The watch bar, three states
| State | What it means | Buttons |
|---|---|---|
| Collecting daily until (a date, green) | New posts using the hashtag are added once a day | Pause |
| Paused (amber) | Nothing is being collected | Resume, Extend 30 days |
| Finished on (a date, grey) | No longer collecting, the report stays as it is | Extend 30 days |
The bar does not appear on link-based reports. Nothing runs for those, so there is nothing to pause.
Pause
Press Pause when you have seen enough. It stops the daily search immediately, which is the point: every day a hashtag report stays on spends real money on scraper runs.
Pausing does not cost you ground. The marker for “when did we last look” is left alone, so when you resume, the report collects everything published during the pause rather than skipping over it.
Resume
Resume turns the daily search back on. It only works while the end date is still in the future. If the date has already passed, the report is finished whatever the switch says, and you are told so rather than being handed a success that would change nothing.
Extend
Extend 30 days pushes the end date out. It adds 30 days to whichever is later, today or the current end date, so extending early does not waste the days you already had.
Two things worth knowing:
- Your plan caps how long a window can be. If the extension would run past that cap, it is trimmed back.
- Extending a finished report also starts it collecting again, because that is what the click means.
The daily top-up
Once a day, every hashtag report whose end date has not passed is swept for posts published since the last run. Each sweep adds at most 100 posts to a report, so one viral hashtag cannot flood it in a single night.
A post has to survive the whole filter chain before it is added:
- Published inside the window being topped up
- Not already on the report, and not one you removed earlier
- Actually carrying one of your hashtags (searches return near misses, especially on TikTok)
- Above your follower minimum, if you set one
Anything that fails a step is counted as skipped, not as an error.
Watching the links land
The Posts card carries three counters: total links, reading… while a link is still being fetched, and failed. They refresh on their own while you watch, and a row that finishes reading updates in place.
A failed row usually means a private, deleted or region-blocked post. Retry re-queues that single link. Anything you typed by hand, such as reach from an insights screenshot, survives a retry, because the background fetch only ever writes what the platform returned.
Removing a post
Deleting a post from a hashtag report also remembers the removal, so tomorrow’s sweep cannot rediscover the same post and put it straight back. The summary figures recompute immediately.
Related
Frequently asked questions
If I pause a report, do I lose the posts published while it was paused?
No. Pausing leaves the last-run marker where it was, so resuming collects everything published during the pause instead of skipping it.
Why can I not resume a report that has finished?
Because the daily sweep filters on the end date as well as the switch, so resuming a report past its date would flip a flag and change nothing. A finished report offers Extend instead, and extending also starts it collecting again.
How often does a hashtag report top itself up?
Once a day. It is deliberately daily and not hourly, because every run is billed scraper time and the product promises new posts once a day.
My link-based report has no watch bar. Is something wrong?
No. The bar only appears on hashtag reports, because only they have a daily sweep behind them. A link report costs nothing to leave open, since nothing runs for it.
A post says "reading" or "failed". What do I do?
Reading means the link is still being fetched, and the counts refresh on their own. Failed means the fetch did not work, usually a private, deleted or region-blocked post. Retry re-queues that one link without touching anything else.