Huntit's clock — your timezone and the rhythms
Huntit runs on one timezone for your whole agency, set when your portal was created.
Every timestamp you see — a post's "found" time, a profile's last check, a report date — is shown in that agency-local time, the same for every member. From there, Huntit's work follows a few steady rhythms.
The two freshness clocks
A profile carries two freshness times, because two different things run on two different schedules.
- Last posts check — when Huntit last looked at this profile for new posts, whether or not any were there. That's the fast rhythm: new posts are found about every 15 minutes, and tracked posts are re-checked on their own schedule.
- Last profile refresh — how recently Huntit refreshed the profile's own details: follower count, avatar and bio. That runs weekly, early Monday.
So a follower count can look a few days old while the posts beside it are current. The follower number updates once a week, not every 15 minutes.
Both times sit on the profile page, so you always know how fresh each figure is.
The weekly and monthly rhythms
| Rhythm | When | What happens |
|---|---|---|
| New posts found | about every 15 minutes | Discovery of new posts on the profiles you track. |
| Profile refresh | early Monday | Followers, avatars and bios are refreshed. |
| Winner calibration | early Monday | Badges are recalibrated against each profile's own recent history. |
| Cleanup | early Monday | Old, unprotected posts past their 12 months are cleared. |
| Usage counters reset | overnight into the 1st | The monthly Posts / Briefs / Comments / Custom counters roll over to zero; the prior month is saved. |
| Reports generated | the morning of the 3rd | The monthly reports are built and the "reports ready" bell fires. In February, May, August and November the quarterly ones are built alongside them. |
All of these are approximate, and all of them run in your agency's timezone.
The counters resetting into the 1st is why a fresh month starts at zero. The previous month's totals aren't lost — they're kept in each client's usage history.