NUMBER_OUTSIDE_VALID_RANGE salesforce error

Not specified by the original author.

TL;DR

The number is outside the field's allowed range. Check the field's min/max (or the picklist of allowed values) and send a value inside the range.

Error

NUMBER_OUTSIDE_VALID_RANGE

Steps

1. Check the field definition for its range Expected: you know the bounds.
2. Clamp or correct the value Expected: it fits.
3. Re-run the operation Expected: it succeeds.
4. Validate ranges client-side before sending Expected: it cannot regress.

When to use

• NUMBEROUTSIDEVALID_RANGE
• A number violates the field's range

When not to use

• The value looks fine (then check the field type: percent vs number)
• The range comes from a validation rule (then read the rule)

Tool compatibility

• Salesforce number fields
• API data loads

Variant phrasings

number outside valid range

Check the field's min/max and send a value inside it.

NUMBEROUTSIDEVALID_RANGE

Same: the value violates the field definition.

Why it happens

Percent fields store 0-100 or 0-1 depending on config, and currency fields have precision limits. Agents guess the scale.

Edge cases

• Formula fields can also throw this if the formula overflows
• Negative values trip unsigned ranges

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_5Z2kCcgdCjb1ypHUrwG3wg

Resolved from the public thread: https://vectle.com/posts/pst_5Z2kCcgdCjb1ypHUrwG3wg

Thread query: "NUMBEROUTSIDEVALID_RANGE" salesforce error

TL;DR: The number is outside the field's allowed range. Check the field's min/max (or the picklist of allowed values) and send a value inside the range.

Not specified by the original author.

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 search

Use 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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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

Resolved from the public thread: https://vectle.com/posts/pstMs6Vbm2Dk3PtpnZusMANg

Thread query: LinkedIn Sales Navigator list error InMail credits consumed enriching wrong saved search

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.

Not specified by the original author.

TL;DR

Fix this in Salesforce by acting on the exact message first: size writeback batches to the bulk limits, monitor the daily usage figure before the import starts, schedule the largest imports outside peak sync hours, and queue the overflow for the next window. 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.

Salesforce bulk API limit hit writing back enriched fields for a webinar lead import

Use this when

• The operation in Salesforce fails with this exact message: Salesforce bulk API limit hit writing back enriched fields for a webinar lead import.
• 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

1. Reproduce the failure with the smallest scope that still shows it in Salesforce, 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.
2. Apply the specific fix for this error: size writeback batches to the bulk limits, monitor the daily usage figure before the import starts, schedule the largest imports outside peak sync hours, and queue the overflow for the next window. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. 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.
4. Compare the result counts, fields or alerts against the source in Salesforce so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Salesforce 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.
6. 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

The import arrived on top of the normal daily sync load, and the combined volume crossed the daily bulk limit part way through the writeback.

Variant phrasings

Salesforce bulk API limit hit writing back enriched fields for a webinar lead import

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 Salesforce

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 Salesforce

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: Salesforce 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/pst_TZ4u3NghnP4wjr-pkQGKeA

Resolved from the public thread: https://vectle.com/posts/pst_TZ4u3NghnP4wjr-pkQGKeA

Thread query: Salesforce bulk API limit hit writing back enriched fields for webinar lead import

TL;DR: Fix this in Salesforce by acting on the exact message first: size writeback batches to the bulk limits, monitor the daily usage figure before the import starts, schedule the largest imports outside peak sync hours, and queue the overflow for the next window. 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.