You do not need to read the flow first. The order of owners on recent leads shows what is wrong.
List the last 50 leads in order
SELECT Id, CreatedDate, OwnerId FROM Lead ORDER BY CreatedDate DESC LIMIT 50Write the owners down in a row. Then match what you see.
The patterns
| Owner order you see | Likely cause |
|---|---|
| The same owner many times in a row | A bulk load gave every record the same counter value. See imports and API loads |
| Pairs of leads with one owner, created seconds apart | Two records read the counter at once. This is a race, and it grows with volume |
| One person never appears | They are missing from the rotation list, or marked away or full |
| Someone who left appears | The list is not tied to who is active. See round robin sending leads to inactive users |
| Owners change after the first row | A second flow or rule takes the lead after the rotation. See a flow overriding the rule |
| The order restarts at the same person | The counter resets, or the list was rebuilt |
Count it yourself
SELECT OwnerId, COUNT(Id) FROM Lead WHERE CreatedDate = LAST_N_DAYS:30 GROUP BY OwnerId ORDER BY COUNT(Id) DESCCompare people in the same rotation. A gap with no reason, such as a part-time rep, points to a pattern above. The options and their faults are in round robin lead assignment in Salesforce.
The free scan cannot count which rep gets each lead. It checks the setup behind it.
Work through it in order
- Run the owner list query and write the last 50 owners in a row.
- Match the row to one line of the table. Name a single cause.
- Run the 30 day count and compare people on the same rotation.
- Fix the cause, then wait for 50 new leads and run the first query again.
Change one thing at a time. Two fixes at once make the next pattern hard to read. The options are in round robin lead assignment.
What to record
| Item | Why |
|---|---|
| The date of each query | The pattern changes as new leads arrive |
| The list of rotation members that day | Someone may have been added or removed |
| The cause you named | You can check it again after the fix |
Check for leavers first. It is the quickest pattern to rule out. See round robin to inactive users.
If you also use HubSpot
HubSpot spreads records equally within a team or between chosen users. It says that adding or removing owners resets the assignment counts. Source: HubSpot knowledge base, rotate record to owner, read on 18 October 2026, page dated 23 September 2026. The same habit helps here: note every change to the list. See HubSpot round robin uneven.
Have it checked every night instead.
Routing Forensics connects as a read-only user and checks this, and the rest of your routing, against your real leads. Three design partners get a free health report on their own CRM, free for 90 days: what is leaking, where, and what it is worth. Apply for a place.
The free scan cannot count which rep gets each lead. It reads your routing setup in your browser. Scan your Salesforce or HubSpot routing. The nightly check, open to design partners, counts it.