LinkedIn Sales Navigator list error InMail credits consumed enriching wrong saved search
Fix this in LinkedIn Sales Navigator by confirm the saved search name, its filters and its result count on screen before any enrichment runs, record the search identifier in the run notes, and stop the run if the count differs from the expected list size. Use when this exact error blocks an enrichment run, import or sync. Not for a platform outage notice or a completed run where only output quality is in dispute.
TL;DR
Fix this in LinkedIn Sales Navigator by acting on the exact message first: confirm the saved search name, its filters and its result count on screen before any enrichment runs, record the search identifier in the run notes, and stop the run if the count differs from the expected list size. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.
Sales Navigator list error, InMail credits were consumed enriching the wrong saved searchUse this when
- The operation in LinkedIn Sales Navigator fails with this exact message: Sales Navigator list error, InMail credits were consumed enriching the wrong saved search.
- The same failure repeats on retry with unchanged inputs.
- A run, import, export or alert is blocked until this item completes.
Not for this skill when
- The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
- The operation completes and you only disagree with its output. That is a quality review, not this failure.
Steps
- Reproduce the failure with the smallest scope that still shows it in LinkedIn Sales Navigator, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
- Apply the specific fix for this error: confirm the saved search name, its filters and its result count on screen before any enrichment runs, record the search identifier in the run notes, and stop the run if the count differs from the expected list size. Verify: one named record now completes end to end with the correct result and the original message does not appear.
- Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
- Compare the result counts, fields or alerts against the source in LinkedIn Sales Navigator so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
- Rerun the original operation in LinkedIn Sales Navigator on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
- Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.
Why it happens
Two saved searches had near identical names, the run opened the wrong one, and enrichment faithfully processed a list nobody intended to spend credits on.
Variant phrasings
Sales Navigator list error, InMail credits were consumed enriching the wrong saved search
The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.
How to fix this failure in LinkedIn Sales Navigator
The how to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.
Troubleshooting this failure in LinkedIn Sales Navigator
The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.
Compatibility: LinkedIn Sales Navigator at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.
Provenance
Resolved from the public thread: https://vectle.com/posts/pstMs6Vbm2Dk3PtpnZusMANg