Something looks wrong — start here
Most of the things that look broken in Huntit are working exactly as designed — a dash where a platform hides a number, a "Calibrating" label while a profile learns its own history, a quiet day on the radar. Find the state you're seeing in the table below, and it points you to the article that explains what it means and what, if anything, to do.
If your exact state isn't listed, it may be a real error — see error pages and getting unstuck, and request support when a page won't recover.
The symptom index
| Symptom | What it usually means | Where to go |
|---|---|---|
| A metric shows — instead of a number | The platform doesn't publish that metric. — never means zero. | Why do I see "—" instead of a number? |
| A profile shows a Calibrating · N of 30 meter, no badges | Huntit is still measuring the profile against its own history — badges unlock at 30 posts. | When badges unlock |
| A post has no Reach badge, only Engagement | It's a still post — an Instagram carousel or a Facebook photo — and those carry no public view count, so there's no Reach axis. | Pools — why Instagram calibrates twice |
| A profile shows a grey Paused badge ("Paused" / "Brand paused" / "Client paused") | A deliberate pause — set on that profile, or inherited from its brand or client. Not a fault. | Pausing tracking |
| A profile shows an amber Needs attention badge | Huntit has stopped collecting it — the note names the cause, and one click restarts it. | A profile stopped collecting |
| An amber line above every page | Something is affecting the whole service, not your account. It clears on its own; adding or restarting profiles on an affected platform waits until it does. | The notification bell |
| A bell says "@handle on TikTok could not be added" | The account is private, empty, unreadable — or the check was interrupted. The bell's own sentence names which. | What happens when you add a profile |
| The form says "This link doesn't name an account" | The link points at no account — a Facebook page with no username, or a platform page. Paste the account's own address. | What happens when you add a profile |
| "…is already being tracked for this client" | This account is already a profile under this client. | What happens when you add a profile |
| Add-profile is still working after a while | The first collection can take a few minutes. If it stops partway, the profile's page says so and carries a restart button. | A profile stopped collecting |
| A post stopped updating | It reached Complete (finished its 30-day life), Not tracked, or Unavailable — not a fault. | A post's tracking life |
| A post you tracked was deleted on the platform | Tracking stops and the status reads Unavailable; everything captured stays, and badges stand. | A post's tracking life |
| A post from an account you don't track shows under a tracked Instagram profile | It's a collab post, made together with the profile you track. | How Huntit finds new posts |
| An old post disappeared from Huntit | Unprotected posts age out after 365 days; badged, favorited, and analyzed posts are kept. | How long Huntit keeps your data |
| "No posts match these filters" / "No winners match these filters" | Your active filters exclude everything. | Clear filters or widen them — see the posts feed |
| "No posts yet" or "No winners in this window" with profiles already added | The message names which: collection is still running, tracking is paused, or profiles need attention. | The 30–60 minute wait |
| "No posts yet" with no profiles added | The tracking chain isn't set up yet — add a client, its brands, then profiles. | Your first client, brand, and profile |
| The radar reads "No tracked [platform] videos in the last 24h" | No videos on that tab have a fresh tracking check-in yet. A quiet day is honest. | The velocity radar |
| The radar's short windows (1h/6h) are empty, 24h is full | Short windows only surface frequently-tracked profiles. | The velocity radar |
| The radar shows "Learning usual pace · N of 10" | The profile doesn't have enough of its own history yet to judge speed. | The velocity radar |
| A notification disappeared from the bell | The bell keeps notifications for a limited time — the entity's own page is the truth. | The notification bell |
| A teammate got your notification | Notifications route to each client's account manager, not to a role. | Account manager ≠ a permission |
| A key shows Not set / Verified / Invalid | Not set = empty · Verified = working · Invalid = the key itself is dead. | Reading your key states |
| A key shows an amber pill (Free plan — upgrade · Account not active · Needs funding · No credits) | The key works; the provider account or plan is the problem. | Reading your key states |
| "My key was rejected" on save or re-test | A specific rejection message → its cause and fix. | Reading your key states |
| A billing alert bell rang (Apify / BrightData / Gemini) | A provider account needs attention; some things pause until it's fixed. | The billing alert bells |
| AI analysis failed (a Brief / Comments / Custom card) | Retryable (busy, sensitive), fix-first (plan, credits), or a policy block. | When an analysis fails |
| A post reads "Not analyzed — the AI couldn't read this post." | The automatic AI read failed. Open the post: it names the reason, and carries a Re-analyze button on three of the reasons. The card says what to expect. | AI discovery |
| A post reads "Not analyzed — over the 5-minute AI limit." | A video over that limit is deliberately not sent to the AI. Metrics, tracking and badges are unaffected. | AI discovery |
| An analysis seems stuck on its status text | A longer video takes longer; a genuinely stalled run flips to Try again on its own. | Running an analysis |
| "No usable comments" on a comments run | Comments exist but are too thin to analyze — too few real ones, or all spam. Not a failure. | Comments intelligence |
| AI stopped analyzing new posts entirely | Your Gemini account is out of credits — posts still arrive, unanalyzed. | Out of Gemini credits |
| A sign-in code expired or never arrived | Codes are short-lived and rate-limited; check spam; you're invite-only per agency. | Signing in |
| "Couldn't send the code" or "Too many sign-in requests" at sign-in | Nothing is wrong with your address — the email couldn't be sent, or you asked for several codes in a short time. | Wait a minute, then request a new code — see signing in |
| "You don't have access" at sign-in | Your agency's owner invites you — Huntit support can't add you. | Signing in |
| A report changed, vanished, or shows an old name | Reports are frozen at generation; a zero-post month is skipped; renames appear next period. | The report honesty rules |
| A report is thin — sections missing on a new client | Designed states — the report never pretends to know more than it does. | The report honesty rules |
| Yesterday's top post is missing from a stored report | A stored report never changes — it's a snapshot of its generation moment. | A stored report never changes |
| You sent a report link to the wrong person | Revoke it — access dies instantly, and you can issue a fresh link. | Revoking a link |
| A month reads "still settling" | Its posts aren't all 30 days old yet, so the numbers aren't final. | How Huntit tells you the truth |
| A growth chart has an amber gap | A check-in was missed; the next reading bridges the gap honestly. | Reading the growth charts |
| A chart starts with found hours after posting | Huntit saw the post late: it was already up when the profile was added, or the platform handed it over late. Tracking runs from found. | How Huntit finds new posts |
| Huntit's numbers don't match the platform's own analytics | Huntit reads public metrics at check-in moments; native dashboards are authenticated. | How Huntit tells you the truth |
| A generic error page, a 404, or a signed-out screen | Refresh or retry first; some states clear on their own. | Error pages and getting unstuck |