Instagram Follower Export Missing Rows: Diagnose the Shortfall
Start with the file's source, then use 13 yes/no checks to diagnose archive range, split files, row ceilings, confirmed rows, deduplication, or terminal state.
On This Page
If an Instagram follower export has missing rows, identify the file's source first. A Meta account archive and a current bounded Instagram Follower Exporter task are different evidence. For an archive, inspect date range, format, ZIP extraction, split files, and filenames. For a current task, inspect target, Followers versus Following, the 100/200/500/1,000-row ceiling, discovered and confirmed rows, deduplication, all 14 columns, terminal state, and current-session access.
Only after choosing the right entry path can you compare a profile count, confirmed rows, and file data rows.
Diagnosis asset: UA-S32-TROUBLESHOOT-TWO-ENTRY-TREE.
START ── Q1: Where did the file come from?
├─ A. Meta account archive
│ A1 Does the date range cover the period you need? NO → Request the right range; YES → A2
│ A2 Is the full ZIP downloaded and actually extracted? NO → Download/extract it; YES → A3
│ A3 Did you identify HTML or JSON and use a matching reader? NO → Identify the format; YES → A4
│ A4 Can you locate follower/following material in this archive? NO → Preserve the tree; do not guess a path; YES → A5
│ A5 Did you inspect every split follower file, not only the first? NO → Count all parts; YES → A6
│ A6 Do filenames plus all part counts still disagree with the symptom? YES → Archive shortfall needs platform review; NO → Range/read/extraction omission
└─ B. Current Instagram Follower Exporter task
B1 Do sourceProfile/sourceProfileUrl identify the target? NO → Wrong target; YES → B2
B2 Is audience the intended followers or following direction? NO → Wrong direction; YES → B3
B3 Is the selected ceiling large enough for the expected rows? NO → 100/200/500/1,000 ceiling; YES → B4
B4 Is the file exactly 14 columns and are data rows=confirmed? NO → File/reader mismatch; YES → B5
B5 Is discovered>confirmed with ID deduplication on? YES → Duplicate IDs removed; NO → B6
B6 Is the terminal result completed or partial with confirmed>0? NO → Handle login/challenge/rate/private/unavailable; YES → B7
B7 Can this session still open the same target and direction? NO → Access boundary changed; YES → Conclude only “N confirmed rows in this bounded task”That is 13 yes/no checks: six for archives and seven for a current product task. Recovery acceptance is not “the number got bigger.” It means the date range or target, direction, and ceiling are explicit; every relevant file is counted; data rows reconcile with confirmed rows where applicable; and the true terminal state is retained.
Disclosure: Web Tidy publishes this guide and develops Instagram Follower Exporter. Product facts were verified in local first-party runtime code on August 31, 2026. Archive pages and a community report are labeled by evidence grade and do not establish SKU32 behavior.
Keep four evidence grades separate
This page does not determine who unfollowed, who did not follow back, or whether an account was deleted or blocked. A Meta archive is not an input to Instagram Follower Exporter; the product does not parse an archive ZIP.
Path A: a Meta account archive has fewer rows
Two freshly opened archive guides recommend checking the requested range, download format, complete extraction, and Followers/Following files. One describes a connections/followers_and_following/ folder and warns that follower data may be split across files such as followers_1.json. Treat these details as [opened vendor guidance], not as a stable official Meta contract.
Here is the anonymized community symptom used in this diagnosis:
Do not declare an HTML archive invalid merely because one viewer accepts only JSON. Record the actual requested format. Do not infer a total after opening only the first follower part.
Path B: the five current-task row gaps
completed only means the current source ended normally or met the chosen ceiling. It is not an exhaustive-coverage certificate. attention is not terminal. The current runtime exports only completed results or partial results with confirmed rows.
Worked diagnosis with a 200-row ceiling
Accept this result only when the 14-column order, target, and direction are correct; file data rows equal 120; and the handoff retains partial / source_error. It does not claim that 200 rows should have appeared or that the list is complete.
When to repair reading and when to rerun
Archive branch: After correcting range, format recognition, full extraction, or omitted parts, recount the same archive. If it remains short, retain the original ZIP and evidence packet for platform review. Do not switch to the product CTA: SKU32 does not read archive files.
Current-task branch: Use sourceProfile, sourceProfileUrl, audience, and the 14 columns to fix provenance, then reconcile the ceiling, discovered, confirmed, data rows, and terminal state. For login, challenge, rate limit, private, or unavailable states, restore normal authorized access first. The exporter does not bypass those controls.
Only when the target and direction remain valid, the current session can access the list, and the task genuinely needs more rows should you explicitly start a new bounded run in Instagram Follower Exporter. A new run does not automatically append, merge, or continue the previous file in the background.
Write an auditable coverage statement
For an archive, record the request time, date range, format, ZIP filename, extraction tool, observed directory tree, all included follower/following parts, and each part's count.
For a current SKU32 task, record the target, Followers/Following direction, 100/200/500/1,000 ceiling, deduplication setting, discovered, confirmed, terminal reason, filename, 14-column check, and data-row count. Use wording such as:
The current session confirmed 120 rows in this bounded Followers task. The result is partial/source_error.
Do not rewrite that as “all followers were exported.”
What missing rows cannot prove
- One absent account does not prove an unfollow, deletion, block, or deliberate action.
- A community archive symptom does not establish a universal cause; vendor folder guidance is not an official permanent contract.
- A current SKU32 run has a maximum selectable ceiling of 1,000. There is no unlimited-row or private-access-bypass mode.
collectedAtis not exact follow time, androwIndexis not follow order.- History retains at most 20 terminal tasks. It does not monitor, fill gaps, or schedule reruns in the background.
- A partial result permits only confirmed rows; a failed or attention state cannot be relabeled completed.
For the SKU32 schema, use the 14-column field dictionary. For an already confirmed partial artifact, use How to Read a Partial Instagram Follower Export.
Frequently asked questions
Why does an official archive differ from the profile count?
Check the requested range, format, complete ZIP, extraction, and every split part. If the shortfall remains after those checks, the evidence supports platform review—not a guessed universal cause.
Why is a completed task still below the profile count?
It may have ended at the selected 100/200/500/1,000-row ceiling. Completed describes the task ending, not exhaustive account coverage.
Why is discovered higher than confirmed?
With default ID deduplication, a repeated account ID is not added again to confirmed rows. File data rows should reconcile with confirmed.
Will rerunning automatically fill the previous file?
No. Every run is separate. A new run does not automatically merge, append, monitor, or resume the old one.
Can a partial file be used?
Yes, when confirmed rows are greater than zero and the terminal result is partial. Keep the partial label and reason with the file.
Does one missing account prove an unfollow?
No. Other explanations include ceiling, access, deduplication, a changing live list, archive-reading mistakes, and non-comparable runs.