Why Was My Lead Routed Even Though it Should Not Have Qualified for Routing?

Loading

Skip to Main Content

Why Was My Lead Routed Even Though it Should Not Have Qualified for Routing?

Understand why a lead was routed even though it shouldn't have qualified, and how to fix the logic.

Nov 13, 2025
Knowledge

Title

Why Was My Lead Routed Even Though it Should Not Have Qualified for Routing?

URL Name

WhyWasMyLeadRoutedEvenThoughitShouldNotHaveQualifiedforRouting6902027e69fe0

Step-by-Step

The lead may have fulfilled conditions in one of the entry nodes (New Lead or Updated Lead)nodes in your router flow that may have caused it get routed to an assignment node. There may have been something else that has actioned the Lead. Steps you can take to check on the lead:

Check Audit Logs and see the path your Lead went down
Add “Routing Action” as a field on your Lead to see if LeanData actioned it
Make sure that it was LeanData that routed your Lead
Check if your Lead was assigned manually or by another application

Check Audit Logs to See the Path your Lead Went Down

Audit Logs provide a visual representation of the journey a specific Lead took from start to finish through a router flow, showing how it hit each node in your flow. For more information on the audit logs, you can download our Audit Log Guide: /articles/Knowledge/RoutingAuditLogsGuide690207e51196a
You may need to make changes to your routing flow if your Lead routing logic is working incorrectly. LeanData Support or your Implementation Consultant/Customer Success Manager can assist you if needed.

To Check the Audit Log for a Lead:

1. Open the LeanData application in Salesforce.

2. On the side menu, click on Routing to expand the menu.

3. Click on Leads (or Contacts, Accounts, or Opportunities as needed).

4. Click on Audit Logs.

5. Scroll through the results as needed or search for a specific record. The easiest way to find a specific record is to enter the record id in the Search Input box in the upper right corner of the screen. The record id is found in the URL for the record and is typically the last 15 or 18 characters:

Add “Routing Action” as a Field on Your Lead to See if LeanData Actioned It

The Routing Action field will show you the last action that affected the lead from LeanData Lead Router. If you see a Routing Action such as “routed - round robin” or “merged” then you’ll know that LeanData actioned on your lead.

For more information on the Routing Actions, you can download our Routing Actions: /articles/Knowledge/RoutingRoutingActionGuide690207ac3af06

To Add Routing Action as a field on a Lead:

1. Log into Salesforce as a System Admin.

2. Open a Lead, Contact, or Account record.

3. Click Edit Layout in the upper right corner of the record.

4. In the object chooser, select the Routing Action field.

5. Click and drag the the Routing Action field onto the Lead Record. Changes are saved automatically

Make Sure that it Was LeanData that Routed Your Lead

You can check the Lead History section for information on who routed the lead. If the LeanData integration user is shown as the user who changed the Lead’s ownership to another user the action was performed by LeanData. If the Lead’s ownership is changed by the another user besides the LeanData integration user, the Lead was assigned by a different user.

Check if Your Lead Was Assigned Manually or by Another Application

It is possible that the LeanData token user is also the token user for other applications, so you should check with your Salesforce administrator to see what other applications the LeanData token user is assigned to.

Typically one of these items should be the source of the issue. If you are unable to resolve your Lead processing issue please contact LeanData Support.

Question? Contact LeanData Support

OrchestrationFAQS & TROUBLESHOOTINGALL

Loading

Why Was My Lead Routed Even Though it Should Not Have Qualified for Routing?