Something looks wrong — start here
Most of what looks broken is a designed state: a dash where a platform hides a number, a profile still calibrating, a quiet day on the radar. Find what you're seeing below. Each row says what it usually means and where it's explained.
If it isn't listed, 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. A dash never means zero. | Why do I see a dash instead of a number? |
A post reads Not measured | No check-in could read it after it was found. Not a fault. | Why do I see a dash instead of a number? |
A count reads Hidden | The post's creator hides it. | Why do I see a dash instead of a number? |
A profile reads Calibrating, with a count of N of 30, and no badges | The profile is still building its own history. Badges unlock at 30 posts older than 3 days. | When badges unlock |
A profile reads Recalibrating | It fell below 30 posts as older ones aged out of the last 12 months. Badges already earned stay; new ones resume at 30. | When badges unlock |
| A post has no Reach badge, only Engagement | It has no public view count (on Instagram and Facebook, anything that isn't a video), or it didn't clear its Reach threshold. | Pools — when a profile calibrates twice |
| An Instagram or Facebook carousel's or image's Engagement reads far lower than a video's | It's a rate of the profile's followers, a video's a rate of its views: two different scales, not a weaker post. | Reach and Engagement |
A profile reads Paused, Brand paused or Organization paused with a grey dot | A deliberate pause, set on that profile or on its brand or your organization. Not a fault. | Pausing tracking |
A profile reads Needs attention with an amber dot | It isn't being collected. Its page names the cause and has a one-click restart. | A profile stopped collecting |
A new profile still reads Setting up after a while | Its first collection usually takes 30–60 minutes — longer for a deeper history, or when you add many profiles at once. The line under the word names the step. | The 30–60 minute wait |
| A disruption notice at the top of the page | New posts from one platform are delayed. Nothing is wrong on your side. | Temporary service disruptions |
A notification says a profile could not be added | The account is private, empty, unreadable or already tracked under another link, or its posts couldn't be collected right now. The notification names which. | What happens when you add a profile |
The form says This link doesn't name an account. | The link points at a post or a platform page, not an account. Paste the account's own address. | What happens when you add a profile |
The form says This profile is already being tracked. | You already track this account as a profile. | What happens when you add a profile |
| A post stopped updating | It reached Complete (the end of its 30 days), Not tracked or Unavailable. Not a fault. | A post's tracking life |
| A post you tracked was deleted on the platform | It reads Unavailable. Everything captured stays, and its 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, made together with the profile you track. | How Huntit finds new posts |
| An old post disappeared | Posts are cleared after 12 months, except winners, favorites and posts with an analysis you ran that returned results. | How long Huntit keeps your data |
No posts match these filters. or No winners match these filters. | Your filters exclude everything. | Press Clear filters or widen them — see the posts feed |
No posts yet. or No winners in this window. with profiles already added | The message says which: collection is still running, tracking is paused, or profiles need attention (see their rows above). | The 30–60 minute wait |
No posts yet. with no profiles added | Nothing is set up yet: add your brands, then the profiles to track. | Your first brand and profile |
| The radar has no tracked posts on a platform in the last 24h | Nothing on that tab has had its first check-in yet. | The velocity radar |
The radar reads Nothing rising right now, or names the measure | No post is above its profile's usual pace on that measure, or the profiles are still learning theirs. | The velocity radar |
| The radar's 1h and 6h windows are empty, 24h is full | Short windows only show frequently tracked profiles. | The velocity radar |
A post reads Learning usual pace and a count out of 10 | The profile doesn't have enough posts of that type yet to judge speed. | The velocity radar |
| A notification disappeared from the bell | The bell keeps notifications for a limited time. The page it pointed to always shows the current state. | The notification bell |
| A teammate got a notification you didn't | It arrived before you joined, or while your organization notifications were off. | The notification bell |
A key reads Not set, Verified or Invalid | Not set is empty, Verified works, Invalid means the provider refused the key. | Reading your key states |
A key shows an amber state, such as Usage limit reached or No credits | The key works; the provider account or plan needs fixing. | Reading your key states |
| A key you pasted was refused | The message under the field names the cause. | Reading your key states |
| A provider alert rang the bell | A provider account or key needs attention, and some things pause until it's fixed. | The provider alert bells |
| An analysis failed with a card instead of results | Some are worth retrying, some need a fix first, and a policy block is final. The card says which. | 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, with a Re-analyze button where a re-run can help. | AI discovery |
A post reads Not analyzed — over the 10-minute AI limit. | Videos over that limit aren't sent to the AI. Metrics, tracking and badges are unaffected. | AI discovery |
| An analysis seems stuck | A longer video takes longer. A run that stalls turns into a Try again card on its own. | Running an analysis |
A comments run reads No usable comments | The comments were too few or mostly spam to analyze. Not a failure. | Comments intelligence |
| AI stopped analyzing new posts | Your Gemini account is out of credits, or Google refused the key. Settings → Credentials shows which. Posts still arrive, unanalyzed. | Out of Gemini credits |
| A sign-in code expired or never arrived | Codes expire quickly. Check spam. | Signing in |
Sign-in says Couldn't send the code or Too many sign-in requests | The email couldn't be sent, or you asked for several codes in a short time. Nothing is wrong with your address. | Use the newest code you received, or try again later — see signing in |
Sign-in says You don't have access to this portal. | Someone on your team has to invite you. Huntit support can't add you. | Signing in |
| Claude can't reach Huntit, or the connection stopped working | Your Huntit access was revoked, you're no longer on the team, or the connector was removed in Claude. | Check you're still a member, then reconnect from Settings → Huntit MCP — see Connect Huntit to Claude |
| A stored report reads differently, or shows an old name | A report is frozen when it's generated. Only its language, its logos and a deleted profile or brand reach it later; a new name shows from the next report. | A stored report never changes |
| Yesterday's top post is missing from a stored report | The report is a snapshot of the moment it was generated. | A stored report never changes |
| A month's report is missing | A month with no counted posts is skipped. | When reports arrive |
| A report is thin, with sections missing | A designed state: the report never pretends to know more than it does. | The report honesty rules |
| You sent a report link to the wrong person | Revoke it. The link stops working at once, and you can issue a fresh one. | Revoking a link |
A week or month reads updating | It holds a post under 30 days old, so a badge can still land. | How Huntit tells you the truth |
| A new profile has no chart yet | The first chart appears the Monday after its first full week. | The Brand page and the evolution band |
| A profile's older posts aren't in its chart | Charts and monthly reports count a profile from the month it was added. | The Brand page and the evolution band |
A week reads Not collected this week. | The profile, its brand or your organization was paused, the format was switched off, or the week falls before the posts collected when the profile was added. The hover names the pause or the switch. | The Brand page and the evolution band |
| A growth chart has a dashed amber line | A check-in was missed, or some of its counts didn't come through. Hover it to see which. | Reading the growth charts |
| A number went down between check-ins | The platform showed fewer: people removed likes or comments, or the platform cleaned out spam. | Reading the growth charts |
A chart starts at found, hours after posting | The post 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 the public numbers at each check-in. The platform's own analytics are private to the account. | 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 |