Recommended Free Tools
Start with the exact error, then check SCAN’s availability, LAMBDA structure, starting value, and the values produced at each step. SCAN returns every intermediate accumulator result, so a formula can have valid syntax yet still produce an unexpected running calculation.
What SCAN does—and the syntax it expects
SCAN applies a LAMBDA to each value in an array and returns the intermediate result after each step. Its documented syntax is =SCAN([initial_value], array, lambda(accumulator, value, body)). The optional initial value sets the accumulator’s starting state; the array supplies the values to process; and the LAMBDA’s body calculates the next state.
As an Amazon Associate I earn from qualifying purchases.
For example, Microsoft documents a running product as =SCAN(1,A1:C2,LAMBDA(a,b,a*b)). For text concatenation, its example is =SCAN("",A1:C2,LAMBDA(a,b,a&b)). These illustrate the function’s structure: the first LAMBDA parameter is the accumulator, and the second is the current array value.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshoot by symptom
SCAN is not recognized
Check that your Excel edition is one of those listed on Microsoft’s SCAN function reference: Microsoft 365, Microsoft 365 for Mac, Excel for the web, Excel 2024, or Excel 2024 for Mac. The reference does not establish availability in every other Excel version, so verify your exact edition before changing a formula that may be valid.
#VALUE! or “Incorrect Parameters”
Microsoft identifies an invalid LAMBDA or an incorrect parameter count as causes of SCAN’s #VALUE! error labeled “Incorrect Parameters.” Check that the arguments appear in the documented order and that the LAMBDA has two parameters: one for the accumulator and one for the current value.
- Confirm the input array is in the second argument position.
- Confirm the LAMBDA names both parameters and uses them in the intended roles.
- Confirm the LAMBDA body calculates the next accumulator value.
To isolate a structural problem, temporarily reduce the formula to a small known input and a simple operation, using names such as a and b. Once that works, restore the intended calculation piece by piece.
#CALC!
Microsoft’s general guidance for correcting a #CALC! error describes conditions such as an unsupported nested array, an array containing range references, or a LAMBDA that has not been invoked. These are general Excel array and LAMBDA cases, not a complete SCAN-specific error catalog.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsInspect what the LAMBDA body returns on each iteration. In particular, check whether it produces a nested array or a range-valued result, and make sure any LAMBDA is being called as part of the formula rather than entered on its own.
The running result is consistently offset or has an unexpected prefix
Check the initial value. It is the accumulator’s starting state, so a starting number or text value affects the running results. Microsoft’s running-product example starts with 1, while its text-concatenation guidance uses "". Choose a starting value that fits the operation instead of changing it at random.
The formula calculates, but an intermediate result is wrong
Select the formula cell and choose Formulas > Evaluate Formula to step through the calculation. When the first unexpected result appears, inspect the corresponding input value, data type, operator, and references in the LAMBDA body. Microsoft’s general formula-error guidance also notes that syntax, arguments, and data types can contribute to errors.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use errors as clues before suppressing them
Keep the original error visible while diagnosing the formula. IFERROR can replace an error with a chosen result, but Microsoft’s error guidance warns that hiding an error does not correct its cause. Wrapping the whole SCAN expression in IFERROR too early can conceal whether the problem is the LAMBDA, input, or calculation body. Use it only when suppressing that error is an intentional part of the finished output.
Quick Recap
A quick isolation sequence
- Identify whether Excel reports an unrecognized function,
#VALUE!,#CALC!, or a plausible but incorrect result. - If SCAN is unrecognized, compare your exact Excel edition and platform with Microsoft’s listed applicability.
- Check the argument order and verify that the LAMBDA has accumulator and current-value parameters.
- Check whether the initial value matches the intended operation.
- For
#CALC!, inspect whether the LAMBDA returns a nested array or range, or whether a LAMBDA is uninvoked. - For a wrong intermediate value, use Formulas > Evaluate Formula and inspect the first step that diverges from the intended calculation.
- Leave
IFERRORoff until the original cause is understood.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
