Exports paused — what the status means
Every exporter in the fleet runs as a background task and can pause itself. When it does, the task row shows Paused · <reason> · <detail> — the reason is the extension's own label for why it stopped, the detail is whatever the site told it. Below is what each documented reason means and what to do about it.
The labels you'll see#
| Reason | What it means | Read |
|---|---|---|
Rate limit | The site decided we asked too often. | Most pauses are rate limits |
Auto_recovery | The extension stopped itself on purpose and will retry by itself. | Most pauses are rate limits / Resume, don't start over |
Auth_error | The site no longer accepts your session. | Auth and session errors |
Unknown | The extension could not read the response — the detail is often something like [object Response]. | When the reason looks garbled |
Free plan limit reached | The free plan's cap for this export is used up. | Plan limits |
The detail is sometimes missing — Paused · Auth_error on its own means the same thing. Match the reason, then follow the link on the right.
Most pauses are rate limits#
The site you're exporting from has decided you made too many requests in a window. The extension detects that, stops, and resumes when the window resets — it pauses automatically on rate limits or network errors and continues when it can. Progress is checkpointed, so nothing is lost while it waits.
Usually there's nothing to do: keep the browser open and let it resume. If it hasn't resumed after several minutes, open the site in a tab in the same browser profile (some sites only refresh their limits while you're active) and press Resume.
Closing the browser or losing the network#
A task survives the tab: progress is written as the export goes, so closing the browser, losing connectivity or shutting the machine down doesn't throw the work away. Re-open the extension and press Resume — it continues from the last saved item instead of starting over.
Auth and session errors#
These exporters have no API keys and no separate login. They act as you, using the session of the site you're already signed into, in the same browser profile. An auth error therefore means the site no longer accepts that session — you signed out, the session expired, the site asked for re-verification, or the extension is running in a different profile / a private window than the one you signed in with.
Fix: open the site, sign in again in the same browser and the same profile, then press Resume. If you use several browser profiles, the extension has to run in the one that is signed in.
Firefox: a container is a separate sign-in#
Firefox multi-account containers keep their cookies in separate stores, and the extension can only read the one that isn't in a container. If you're signed in on the site inside a container, the extension sees a signed-out browser — usually without pausing. The task just finishes with nothing in it, or with the data of whichever account is signed in outside the container. Chrome, Edge, and Safari have no equivalent, so this only applies on Firefox.
This isn't a shortcut on the extension's side: a background request has no way to name a container. Mozilla tracks that gap in bug 1670278, open since 2020. Until it lands there is no supported way for an export to use a container's session.
Fix: open the site in a normal tab, outside any container, sign in there, then run the export again. Running the export from a container tab makes no difference — the extension's own session never follows a tab into a container.
Plan limits#
Free tiers cap how much a single task can do — a number of records per task or of items per export, depending on the product. When a task reaches its cap it stops instead of looping forever, and the task row is how you find out. Each product page lists its own caps and what Pro removes — the extensions section on the home page links to every product page.
When the reason looks garbled#
Sometimes the detail is not a sentence — for example a reason of Unknown followed by something like [object Response]. That is the extension failing to read the response the site returned, not a new kind of limit. Retry the task once. If the same detail comes back, report it with the product name, the exact status line and the time: it usually means the site changed a response the extension doesn't understand yet.
Resume, don't start over#
Resume continues from the last saved item. Starting a fresh task from the top re-fetches everything, which spends the rate-limit budget you just waited for and is usually slower. Start over only when you changed a setting that affects the output itself.