Skip to content

Troubleshoot a prospecting run

Use the affected run's status and event timeline to fix setup, credit, profile, and low-yield problems.

When to use this

Use this when a run will not start, stops early, delivers fewer records, or shows Failed, Blocked, or Setup required.

Requirements and availability

  • Identify the exact run and latest customer-visible event before changing settings or retrying.

How to do it

  1. Open Runs.
  2. Open the run and record status, requested and delivered counts, and latest event.
  3. For Setup required, complete the named setup.
  4. For Quota reached, reduce the research budget or add credits.
  5. For Partial, No prospects, or Stopped (low yield), review requirements and exclusions, then widen one profile dimension.
  6. Retry only after the prior run is terminal and the cause changed.

Fields and controls

Controls in Leama
ControlWhat it does
Try againRepeats a failed page read; it does not claim a run succeeded.
Retry / ResyncRepeats the named setup operation.
View logOpens the selected run's events.
Run agent / Run nowStarts a new run after correction.

What happens next

A corrected prerequisite allows a new request to queue or run. Relaxing targeting can improve yield but does not guarantee target.

States you may see

Customer-visible states
StateMeaning
Setup requiredA named setup step is incomplete.
Quota reachedCapacity is insufficient.
FailedAn operation ended the run.
BlockedA prerequisite or restriction prevented progress.
Stopped (low yield)Sourcing was not finding enough qualified records.
Partial / No prospectsThe run completed below target.

Credits and usage

A retry starts a new credit-consuming run. Inspect the terminal state first.

Common problems

Problems and next steps
ProblemWhat to check
No profile is selectableCreate and save a complete profile.
Credits appear available but insufficientEffort and Phone number can reserve more than one credit per requested prospect.
The same failure repeatsContact support with run, time, status, and exact safe error.