Scheduled Routing Insights Numbers Not the Same as the Number of Records Processed and No Failures? Follow
LeanData begins processing the records immediately when a scheduled 1x routing job is initiated. The time it takes to perform record updates and conversion varies based on the processes running within your Salesforce instance.
Once routing actions such as field updates and owner assignments have been performed successfully, the processed records will be displayed on the Routing Insights page under Deployment History. Each One-Time Job will be considered its own deployment.
If routing actions have not been successfully completed, no audit log will be available and the record will not show on the Routing Insights page for that One-Time Router Deployment.
What to Check?
If the Routing Insights number displayed under the Deployment History is not the same as the number of records processed and no failure is showing, please follow these steps below to troubleshoot:
Check the Apex jobs within Salesforce instance to view if there’s an error on the Apex job.
You can also run a the SOQL query within the Salesforce Developer Console to see if there’s a backlog within the org.
SELECT LeanData__Lead__r.ID,LeanData__Lead__r.Company,LeanData__Account__r.Name,LeanData__Account__c FROM LeanData__Lead_Conversion__c
If there’s no backlog, you can run a report within Salesforce to ensure that the records have not been converted. If the records have already been converted LeanData will not be able to convert the records again and it will not show up as a failed job.
When there’s a backlog of conversion jobs to perform, LeanData will not populate the audit log or update the Routing Insights for that Deployment, since the final action has not yet been completed.
Conversion jobs are performed by Salesforce, and LeanData has no control over how quickly conversions can be completed. If there are errors due to the size of the conversion batches, LeanData support can help adjust these batch sizes.