Continue a stopped enrichment

An enrichment run that cannot go on stops and tells you why in the task indicator. You don't have to set anything up again: Continue picks the run up where it stopped, and nothing that was already enriched is charged a second time. This article is about that button; "Enrichment runs: progress, limits and stopped runs" explains how runs work in general.

Why a run stops#

There are three reasons, and the task indicator shows the exact sentence:

• "Stopped: not enough credits — N of M left. Top up and start again; what was done is kept." The balance no longer covers the next group of rows. In a workspace every run spends the workspace owner's credits, and the balance is checked before every group — so a run can stop halfway when other members spend the same credits at the same time.
• "Stopped: the provider is not answering — N left. Try again later." The data provider behind the lookup returned only errors for three rounds in a row, or reported an invalid key or exhausted credits on its side. ListPlus stops instead of retrying blindly.
• "Stopped at the accepted maximum of X credits — N left." The run has spent the amount you accepted when you started it, and rows are left.

In all three cases the rows already done keep their results and their filled cells, and the rows that are left were not charged.

What the task indicator shows#

Click the pill at the top of the screen to expand the panel. A stopped run has a red cross in front of its name, the reason in red below the counts, and two buttons on the right: Continue (with a play icon) and Dismiss (×). The counts show how many rows succeeded, how many failed and how many came from the cache, plus the credits spent so far. Dismiss only removes the entry from the panel — it does not cancel anything, and the run can still be continued by starting the same enrichment again (see below).

What Continue does#

Continue resumes the very same run on the server with the rows that are still open. Rows already enriched are finished and are not looked at again; the open ones carry on in groups, with the balance checked before every group as before.

• After "not enough credits" — top up first (in a workspace, the owner). Continue keeps the accepted maximum you set at the start; if the balance still doesn't cover the next row, the run stops again at once with the same message.
• After "the provider is not answering" — wait a little, then Continue. The error count starts from zero; if the provider is still down, the run stops again after three error-only rounds.
• After "accepted maximum" — Continue lifts the ceiling: the run goes on until the open rows are done or the balance runs out. If you want a new ceiling instead, start the enrichment again from the dialog with a smaller selection.

Continue works only on a run that stopped by itself. A run you cancelled with Stop, a finished run, or a scraper import cannot be continued — start them again instead. A stopped run and its open rows are kept for 48 hours; after that, starting the enrichment again is the way to finish it.

Starting again instead of Continue#

You can also start the same enrichment again on the same rows — for example when the Continue button is no longer there. The result is the same: rows that already have a result are served from the cache and cost nothing, and the rows that are left are enriched. Two details:

• Rows that an active run is still working on are skipped by a new run of the same kind, so two runs never pay for the same row. Rows of a stopped run are free to take.
• A row whose earlier lookup found nothing is looked up again (only results are cached), with the usual charge rule for that lookup — e-mail and phone lookups charge only on a hit.

Where the accepted maximum comes from#

When you start an enrichment from the fields dialog, each pattern shows "≈ X Cr" and "at most Y Cr" (or just "at most Y Cr for N contacts" when the two are close); the footer sums it up as at most Z Cr. That "at most" is the ceiling of the run: the route's maximum per record times the records in the pattern. The run checks it before every group, so it never spends more than you accepted — and stops with "accepted maximum" when rows are left. An enrichment that was started without an "at most" figure has no ceiling beyond the balance.

Related topics: running-jobs-and-limits · enrichment-problems · enrichment-found-nothing · fill-empty-cells · credits-explained.

FAQ#

Will I be charged twice when I continue a stopped enrichment?#

No. Continue resumes the same run with the rows that are still open; rows already enriched are finished and not touched again. If you start the same enrichment again instead, rows that already have a result come from the cache at no cost and only the rows that are left are charged.

Why did my enrichment stop?#

Open the task indicator at the top of the screen: the reason is written in red under the run. It's one of three: "not enough credits" (the balance doesn't cover the next rows — in a workspace it's the owner's balance), "the provider is not answering" (the data provider returned only errors for a while) or "accepted maximum" (the run spent the amount you accepted at the start). Rows already done keep their results.

How do I continue a stopped enrichment?#

Click the pill at the top of the screen, then Continue next to the stopped run. It goes on with the rows that are left; after "not enough credits" top up first, after "accepted maximum" the ceiling is lifted and the run finishes the open rows. If there is no Continue button any more, start the same enrichment again on the same rows — enriched rows are not charged again.

Can I continue a stopped import?#

No. A LinkedIn or scraper import that stopped cannot be continued, because the provider's run is over; start the import again. Enrichment runs are different: those can be continued or simply started again without paying twice for finished rows.

The Continue button is gone after a reload — what now?#

The task indicator only lists runs started in this browser session, so after a reload (or on a colleague's screen) a stopped run isn't shown. Start the same enrichment again on the same rows: it continues with the open rows, and rows that already have a result are served from the cache at no cost.

I topped up, clicked Continue, and it stopped again — why?#

The balance is checked before every group of rows, so the run stops again as soon as it can't cover the next row — in a workspace other members may be spending the owner's credits at the same time, or the top-up didn't cover the rows that are left. Check the balance at the bottom of the navigation bar, top up for the remaining rows, and click Continue again; everything done so far is kept.

Does Continue keep the maximum I accepted?#

Yes, except after a stop at the accepted maximum: then Continue lifts the ceiling, because the old one would stop the run again at once. After "not enough credits" or "provider not answering" the accepted maximum stays as you set it.