Why is LeanData Taking So Long to Process my Leads?

Troubleshoot why LeanData is taking a long time to process leads. Causes and how to speed it up.

  • May 13, 2026
  • Knowledge

Title
Why is LeanData Taking So Long to Process my Leads?
URL Name
WhyisLeanDataTakingSoLongtoProcessmyLeads6902028a9932f
Step-by-Step
LeanData operates within Salesforce and our Apex jobs run alongside all of your other apps and processes. As a result, processing time will vary based on how many other Apex jobs/processes are running within your Salesforce alongside LeanData.
If there are several other Apex Jobs running that take up all of the available Apex processing job slots, LeanData’s jobs can temporarily be deprioritized. This means that LeanData processing can be delayed as the other jobs are preventing LeanData from running our jobs in a timely manner. Consequently, the processing of new and updated Leads, Contacts & Accounts would become delayed until enough job slots have opened up for LeanData to resume normal processing.
If you notice that LeanData’s processing is taking longer than usual, there are a few things you can check to help diagnose what is causing the delay.
First thing to check is the LeanData job status within the LeanData app. 

To check the LeanData job status:

  1. Open the LeanData App and the job status will be displayed in the upper left corner.
  2. OR from within the LeanData App, navigate to Admin > Settings, and the LeanData job status will be displayed in the LeanData Job Scheduler section

User-added image

When checking the job status, please note that there are a few different status options that can be displayed. Please see the definitions of each below.

 

LeanData Job Status:
  • Running: Queued, Preparing, Processing: Queued, Preparing, Processing
  • Running - Delayed: Processing but there are backlogs. LeanData jobs are 12 hours behind processing
  • Holding: Holding - If there are 5 currently running apex jobs and LeanData needs to wait until one of those 5 slots becomes available
  • Aborted (job needs to be restarted): Aborted. Your salesforce instance has hit the governor limits and LeanData was unable to place the jobs in the queue to be processed.
  • Failed: Failed please check the apex job for error message and contact IT
  • Not Running: LeanData’s jobs are not running at all. Please check the Salesforce Apex job Queue and remove the non-essential jobs. Restart the LeanData scheduler.

User-added image

If the job Status is other than “Running”, proceed to check your instance’s Apex jobs. Salesforce has a limit of 5 total active job slots for each organization. If there are more than 5 active jobs, the jobs will be queued and will run as the slots open up accordingly.
By checking the Apex Jobs, you can see if there are any unnecessary or non-essential Apex jobs that are processing and have deprioritized LeanData. If you find any non-essential jobs occupying a job slot, you can abort the job to open the slot up for another queued job.
The maximum number of Apex Jobs that can be added to the scheduled job is 100. If there are already 100 jobs queued up within your instance, your instance will hit the Salesforce governors limit.

 

Questions? Contact LeanData Support

AdminFAQSALL