Instagram Follower Export Partial Results: Paused vs Partial vs Failed

A partial Instagram follower export is a downloadable terminal result: the run ended after Stop, an interrupted execution context, or a source failure, but at least one row had already been confirmed. paused is a non-terminal wait inside the same task. failed is terminal with confirmed = 0, so there is no file to export—and it is never evidence that the target has no followers.

Read the current phase first, then terminalReason, then confirmed. Whether a file happens to open cannot replace those three checks.

What this page diagnoses#

This guide answers one narrow question for INS Follower Exporter: when paused, attention, completed, partial, or failed is shown, are the current rows downloadable, what conclusion can they support, and does the next action mean Resume, explicit Retry, or a separate new task?

It does not explain why one account is missing, recover a browser download after a valid artifact already exists, or bypass login, challenge, rate-limit, private, or unavailable access gates. Use missing rows for coverage and download not working for browser-save and file recovery.

Eight visible task states#

completed means the scheduler ended normally. The source may have ended, or the selected 100, 200, 500, or 1,000-row cap may have been reached. It does not automatically mean complete account history.

Same settings, different terminal results#

Use one anonymous input throughout: @sample_creator, Followers, a 500-row cap, and CSV. Only the observed terminal event and confirmed count differ.

The same input does not guarantee the same coverage. A later run is not a seamless continuation of an older partial file.

Text diagnosis tree: phase to terminalReason to confirmed rows#

1. Is the phase paused? Resume continues the next page under the same run ID. Stop moves through stopping. Nothing is downloadable yet, and a parallel new task is not the recovery action.
2. Is the phase attention? Read the error: authorization_required, login_required, challenge_required, rate_limited, or private_or_unavailable. Restore normal Instagram access first. Explicit Retry starts a new task; it is not Resume.
3. Is the phase completed? Its reason is completed. Download only when confirmed > 0, then describe the result relative to the selected cap rather than claiming complete account history.
4. Is the phase partial or failed? Read the reason. stopped means user-requested Stop; interrupted means a live local task was recovered after its execution context disappeared; source_error means the source request could not finish.
5. Is confirmed > 0? Any of those three early endings becomes partial. The confirmed rows are downloadable. Preserve target, Followers/Following direction, selected cap, reason, count, and collection time.
6. Is confirmed = 0? Any of those endings becomes failed. There are no downloadable rows. The only supported conclusion is that this run produced no deliverable result.
7. Do you still need a new run? Start one only after the access gate is resolved and the old artifact is insufficient. Keep it as a separate snapshot. Do not merge runs unless a downstream reconciliation explicitly checks ID, target, direction, time, and cap.

Retry is not Resume#

Five checks before using the file#

1. Record the final phase and terminalReason.
2. Confirm confirmed > 0 and that the phase is partial or completed.
3. Open CSV or XLSX, verify the 14-column header, and match data-row count to confirmed.
4. Check sourceProfile, audience, collectedAt, rowIndex, and the selected cap.
5. Label every downstream copy as partial/{terminalReason}/{confirmed} when applicable.

A copyable anonymous note is: @sample_creator / followers / cap 500 / partial / stopped / confirmed 180 / collected 2026-08-31.

Limits that remain after a successful download#

• Partial proves only that these rows were confirmed locally; it does not prove omitted accounts do not exist.
• Completed is still bounded by the selected 100–1,000-row cap, current session visibility, and source responses.
• Local History keeps at most 20 ended or attention-required tasks. It is not cloud backup, scheduled monitoring, or an unlimited recovery queue.
• A new task has a new time and access context. The product does not auto-merge tasks or infer relationship changes.
• No phase authorizes bypassing Instagram controls, endless retry, or inferring the target's true total from a partial or failed run.

Frequently asked questions#

What is the difference between paused and partial?#

Paused is non-terminal and Resume continues the same task. Partial is terminal and exposes only the rows already confirmed; the original task cannot continue.

Is every partial result downloadable?#

Under the current runtime contract, yes: partial necessarily means confirmed > 0. If the browser did not save the file, use the download recovery guide before collecting again.

Does failed mean the profile has no followers?#

No. It means the run ended with confirmed = 0; it says nothing about the target audience total.

Does Retry in attention continue the old task?#

No. Explicit Retry calls Start and creates a new task. Only Resume from paused continues the same task.

Can I click Retry repeatedly after a rate limit or challenge?#

Do not. Resolve normal access in Instagram first. The internal three-attempt rule applies only to transient network failures or HTTP 5xx responses.

Can I append a later run directly to the partial file?#

Not by default. Times, sessions, caps, and source visibility can differ. Merge only through an explicit, provenance-preserving reconciliation keyed by ID.

Choose the next route after diagnosis#

• Use Instagram Follower Exporter only when access is normal and a separate bounded run is actually needed.
• Use download recovery when a completed or partial result exists but the browser did not save or open it.
• Use missing-row diagnosis for coverage questions.
• See the complete export guide for method selection and output boundaries.

The public comparison set was rechecked against Unfollowfy's Instagram data export guide, Web Tidy's complete follower export guide, and CommentGrid's export guide. Those pages cover archive splits, broad export steps, and incomplete outputs; the state tree above is based on the current SKU32 runtime and distinguishes product terminal reasons from official-archive file splitting.