Instagram Post Sorter Shows No Posts
Diagnose zero candidates by separating the route, access, grid, loading, and collector states.
On This Page
Instagram Post Sorter Shows No Posts
If a run starts but returns zero candidates, separate four conditions in order: an unsupported URL, a profile the current session cannot access, a grid that has not loaded yet, and a visible grid whose cards were not collected. Only the last case warrants one controlled reopen and escalation. A private or inaccessible profile, a genuinely empty grid, and a missing grid are not collection barriers to bypass.
INS Sorter only reorders the currently loaded cards on a supported Instagram profile grid in your browser. It does not read a profile's complete history, change the public grid, or access private Insights.
Read the page evidence before the number
The four counts answer different questions: scanned is the cumulative set of unique cards seen during the run; collected is the saved snapshot count; currentCandidates is the set currently eligible for sorting; sortedDisplayed is the set actually reordered on screen.
Zero-result diagnosis tree
START: currentCandidates = 0
├─ Not on instagram.com/username/?
│ └─ Open the profile root → stop if it is still unsupported
├─ Instagram itself cannot show the profile?
│ └─ Login/challenge/private/access error → stop; do not bypass
├─ Main grid has not appeared?
│ └─ Let the page settle → refresh once → stop if still missing
├─ Grid exists but truly contains no post cards?
│ └─ Accept the explained empty-grid result → stop
├─ Cards are visible while all four counts remain zero?
│ └─ Record the state and reopen the extension once on the same route
└─ Same visible grid still produces zero?
└─ Stop retrying → submit minimal, non-sensitive evidenceVerification checklist
- The URL is a one-segment profile root.
- Instagram itself is accessible in the current session.
- You recorded exactly one state:
grid missing,grid empty, orvisible cards but zero collector. - You recorded all four counts.
- You used at most one refresh or one same-route reopen, not a chain of both.
- If visible cards still produce zero, you stopped and preserved evidence.
Useful escalation evidence is limited to browser and extension versions, non-sensitive URL type, visible status text, the four counts, reproduction time, and whether cards are visible. Never send a password, cookie, token, or private post content.
Limits and next step
Third-party troubleshooting pages show that “no posts” is ambiguous, but they cannot identify the SKU10 cause. This workflow does not compare another account, infer deleted or archived history, or circumvent access. Zero describes only this session and currently loaded surface—not complete history.
If cards are visible and one same-route reopen still returns zero, use the broader not-working checklist. If the profile is supported, accessible, and visibly has loaded cards, open the INS Sorter product page. If the page is inaccessible or truly empty, stop: reinstalling cannot change that boundary.
FAQ
Does zero mean the account has no posts?
No. It can mean an unsupported route, inaccessible page, missing grid, genuinely empty grid, or a collector mismatch. Record the grid state first.
Can the extension read a private profile?
It is not an access-bypass tool. Only a supported profile grid already visible to the current session is in scope.
Should I keep scrolling until results appear?
No. Scrolling cannot make a missing grid ready or create cards in a truly empty grid.
Why only one refresh or reopen?
A single controlled action preserves a before/after comparison. Repeated refreshes erase the evidence needed to classify the failure.