Instagram Post Sorter Stuck Loading Posts
Preserve and verify the loaded snapshot when progress increased and then stopped, with at most one bounded retry.
On This Page
Instagram Post Sorter Stuck Loading Posts
If the count increased and then stopped, click Stop once, record scanned / collected / currentCandidates / sortedDisplayed before and after, and verify that the currently loaded set remains sorted by the selected field and direction. A loading → stopping → stopped transition with a verifiable partial set is a useful bounded result. If the page is stable, allow at most one retry with identical settings; stop and escalate if it stalls at the same or an earlier count.
Do not call a never-started run, an initial zero result, a missing metric, or a navigation reset “stuck loading.” INS Sorter only reorders the currently loaded profile-grid set in your browser. Stop does not prove complete history or change the public grid.
Define the symptom first
This page applies only when the state entered loading, scanned or collected increased at least once, and then stopped increasing while the route remained unchanged. The runtime itself ends when the target is reached, Stop is requested, or repeated passes reveal no new unique cards. The goal is to turn progress into a verifiable partial snapshot—not force “all posts.”
Record this before acting:
profile route: /username/
sort field: Likes | Comments | Views | Date
direction: High to low | Low to high
load target: 25 | 50 | 100 | 200 | 1,000 | All
status before Stop: loading
scanned / collected / currentCandidates / sortedDisplayed: __ / __ / __ / __
last observed increase at: __
status after Stop: stopping → stopped | other: __The counts need not match because Instagram can virtualize and remount cards. scanned is cumulative unique cards seen; currentCandidates and sortedDisplayed concern the current page surface.
Stuck-loading diagnosis tree
START: loading appears not to progress
├─ Never entered loading and no count ever increased?
│ └─ Not stuck → use the general not-working diagnosis
├─ currentCandidates was zero from the start?
│ └─ Not stuck → use the no-posts diagnosis
├─ Only one metric is missing on some cards?
│ └─ Not stuck → preserve missing; change field or stop that sort
├─ Counts increased, then stopped on the same profile?
│ └─ Record → Stop once → wait for stopped
│ ├─ Partial set remains and order verifies → accept partial result
│ └─ State/set contradicts the readback → stop and escalate
├─ Stable page and a larger set is still necessary?
│ └─ Retry once with identical settings
│ ├─ Passes first stopping point → continue to a bounded end
│ └─ Stops at same/earlier point → stop and escalate
└─ Refresh, tab/profile switch, or route change occurred?
└─ Not the same stuck run → record reset and establish a new baselineSix-step recovery
- Keep the tab, profile, and route fixed; copy the progress card.
- Click Stop once—do not refresh or navigate at the same time.
- Wait for
stopping → stoppedand confirm the loaded set remains. - Verify the first three rows: source-post identity, field evidence, and direction.
- End if the partial set is sufficient. Otherwise retry once with identical settings on a stable page.
- If it stalls at the same or an earlier count, preserve both cards and escalate.
Hard stops include a login/challenge/access restriction, an unexplained state or missing set after Stop, and a controlled retry that stalls at the same or earlier point.
Verification and limits
A valid partial result has a stopped or target-reached terminal state, all four counts, unchanged field/direction/target, three verified source-post rows, and explicit “currently loaded set” wording. If retried, the retry count is exactly one.
Third-party documents support keeping context and bounding retries, but their workspace, follower-scan, upload, and archive behaviors do not define SKU10. All continues under the current page conditions until a bounded end; it is not a promise of complete account history.
For a run that never started or initially returned zero candidates, use the matching branch in the general not-working checklist. If a verified partial set is useful, continue from the INS Sorter product page.
FAQ
Does Stop discard loaded posts?
The normal path is loading → stopping → stopped, preserving and sorting the current set. Verify it with the counts and first three rows.
Why can All stop?
It is not a complete-history guarantee. The current page may stop exposing new unique cards or the run may reach another bounded terminal condition.
Can I keep refreshing to continue?
No. Refreshing resets the page context and destroys comparability between stopping points.
When is one retry allowed?
Only on the same stable route with the same field, direction, and target, when a larger set is still necessary.