Find the next thing to check.

A #FIELD! result needs an actual record and a field that belongs to it.

1. Inspect the attached field table in the local example. A plain label or a concatenated text result does not carry a record. Equal labels can belong to different source cells.
2. Check the field name or the cell that supplies it. An existing zero, FALSE or empty text field is different from an absent field. Preserve an upstream calculation error while fixing its source.
3. A source-label change suspends its old local fields. Apply replacement record JSON whose labels match the current source, or reset the example. This local data is not a connected Stocks or Geography feed.
4. Download fixed results with the record audit, or keep the JSON for local practice. These workbooks do not serialize native linked data types; native FIELDVALUE recalculation requires its own real data-type source.

• Inspect and edit local record fields →

Reference: Microsoft: FIELDVALUEMicrosoft: #FIELD!

A #SPILL! result needs its output area checked before changing the formula.

1. Keep the formula in its anchor cell. Move or clear entries in the intended output area, including entries below a shorter result.
2. In these lessons, use the stated reserved output area. Changing a filter can make a report grow again; a currently unused cell still needs to stay clear.
3. Native Excel also checks merged cells, worksheet edges and table placement. Clearing a blocker addresses one cause; it does not diagnose every spill error.

• Try an editable filtered queue →
• UNIQUE examples →

Reference: Microsoft: #SPILL!

#NAME? can come from a spelling, declaration or support problem.

1. Compare the function spelling and argument order with its reference. Text labels in a formula need double quotes.
2. A LET name or LAMBDA parameter belongs to its declared scope. Check the declaration and the place where it is called.
3. Open the function reference to check this site’s support boundary. A browser #NAME? alone does not prove the formula is invalid in your Excel version.

• LET examples →
• LAMBDA examples →

Reference: Microsoft: formula errorsMicrosoft: LET

#VALUE! calls for checking the actual values and range shapes passed to a function.

1. Read the referenced cells, not only their display format. A number-looking string and a number can behave differently.
2. Check that paired ranges describe the same records and that a filter mask fits the data it selects.
3. For imported numeric text, decide its decimal and group separators explicitly. Formatting a label as Number is not a conversion rule.

• Convert imported numeric text →
• NUMBERVALUE examples →

Reference: Microsoft: formula errorsMicrosoft: NUMBERVALUEMicrosoft: FILTER

#REF! indicates a reference that cannot be used; replacing the displayed error does not repair it.

1. Inspect the formula for a deleted reference or a range outside the intended source.
2. Trace each argument back to its source cells. For an INDEX lookup, compare the requested position with the source dimensions.
3. Rebuild the intended reference, then recalculate and check another dataset.

• INDEX examples →
• Practice a two-way lookup →

Reference: Microsoft: formula errorsMicrosoft: INDEX

#DIV/0! can expose a zero base or an average with no numeric observations.

1. Inspect the denominator and the selected record count. A measured zero and no observations need separate business rules.
2. Decide what to show when the base is zero: an explanatory label can be more useful than inventing a percentage.
3. Test zero, positive and negative bases. Use an error handler only after choosing which condition it represents.

• Practice percentage change →
• Practice a weighted mean →

Reference: Microsoft: formula errorsMicrosoft: AVERAGE

#NUM! can mean that a numerical argument lies outside the function’s allowed domain.

1. Read the argument limits on the relevant function page. Do not change a sign or a unit just to remove the error.
2. For an iterative financial calculation, inspect the cash-flow sequence and starting assumptions before choosing a different guess.
3. Compare a small supported example with your input and identify which assumption differs.

• SQRT examples and domain →
• IRR examples →

Reference: Microsoft: SQRTMicrosoft: IRR

A missing exact record and a nearest-lower quantity band require different lookup rules.

1. For an ID, begin with exact matching and inspect numeric/text types and spaces if the record is missing.
2. For a band table, define whether a boundary belongs to the lower or upper band. XLOOKUP match mode -1 chooses an exact or next-smaller key.
3. A binary search requires the documented sort order. Handle a genuine missing match with a chosen label; keep unrelated errors visible.

• Exact record lookup →
• Quantity-band challenge →

Reference: Microsoft: XLOOKUP

A FILTER report needs an explicit no-match outcome when an empty selection is expected.

1. Check whether the selection is genuinely empty or whether its criteria are wrong.
2. FILTER has an if_empty argument for a chosen no-match value. A compound report may instead check its selection count before sorting.
3. Retest the no-match case and a nonempty case. Other unsupported array operations can also produce #CALC!; this is a starting point, not a universal fix.

• FILTER examples →
• Queue with a no-match case →

Reference: Microsoft: FILTER

The browser’s #CYCLE! label means a calculation depends on itself.

1. Check whether the formula includes its own cell directly, then trace formulas in the cells it reads.
2. Separate source data from the output range. A running total can use prior state without including its own output cell.
3. This learning worksheet does not offer native iterative-calculation settings. Repair the dependency and recalculate.

• Build a running balance with SCAN →

Reference: Microsoft: formula troubleshootingMicrosoft: SCAN

Check the opening equals sign, quotes, parentheses and argument separators.

1. Start with = and balance parentheses outside quoted text. Double quotes delimit formula text; a doubled quote escapes a quote within that text.
2. This browser editor uses commas between function arguments. A semicolon inside an array constant has a different role; do not replace every semicolon blindly.
3. Structural hints do not evaluate a formula or validate its whole grammar. Use Calculate or Apply formula, then inspect the actual result.

• Explore IF arguments →

Reference: Microsoft: formula troubleshooting

An asterisk in criteria can select more records than the label you intended.

1. Decide whether the symbol is part of the stored label or a wildcard. Test a literal P* label alongside Pine so an overly broad match becomes visible.
2. Excel criteria use ~ to escape a wildcard character. Operator equality and a criteria-function pattern are separate operations.
3. Use the literal-label guide and its counterexample. Some guided tasks accept a narrower criteria contract and leave unsupported inputs ungraded.

• Literal labels and wildcards →
• COUNTIF examples →

Reference: Microsoft: wildcard characters

Calendar dates, working dates and timestamp boundaries answer different questions.

1. For a monthly timestamp report, an inclusive start and exclusive next-month start avoid dropping records later on the final day.
2. For working dates, declare the weekend and holiday calendar. WORKDAY.INTL returns a date; NETWORKDAYS.INTL counts working dates in an interval.
3. Check a boundary record, a weekend and a holiday. The local lesson explains its accepted serial-date inputs.

• Choose a working calendar →
• Multi-condition date report →

Reference: Microsoft: WORKDAY.INTLMicrosoft: NETWORKDAYS.INTLMicrosoft: SUMIFS

A recorded zero contributes to a numeric mean; a blank does not represent a measured zero.

1. Name the unit being averaged: records, groups or weighted amounts. An average of group averages need not equal the record-weighted result.
2. Count numeric observations, including zeroes. Review text numbers before deciding whether to convert or exclude them.
3. Test an all-empty group and a measured-zero group separately. Preserve record order and repeated labels when computing row means.

• Why averages need their counts →
• Row-wise review averages →

Reference: Microsoft: AVERAGE

Relative references move with a copied formula; dollar signs lock the chosen coordinate.

1. Compare the first formula with the next row or column. A2, $A2, A$2 and $A$2 lock different coordinates.
2. Keep fixed controls and source ranges locked where required, while allowing each record reference to move.
3. Apply and fill the formula, then inspect a distant answer cell. A single-anchor spill task should not be filled into its children.

• Practice reference locking →

Reference: Microsoft: reference types

SCAN, BYROW and MAP give a LAMBDA different inputs and expect different outputs.

1. SCAN passes the previous state and current value to a two-parameter LAMBDA; its output contains the successive states.
2. BYROW supplies one row at a time and expects one result for that row. Name parameters for what they receive, not for worksheet addresses.
3. Check required arguments and scope, then test a reordered source or an empty row. Optional-parameter examples have their own documented browser limits.

• Running balance task →
• BYROW examples →
• ISOMITTED examples →

Reference: Microsoft: SCANMicrosoft: BYROW

A formula can fit one table and fail another; practice checks its reusable behavior.

1. Open the results by dataset after a check. Current worksheet failures and separate test cases are labelled independently.
2. Compare the first failing result with the task rule. A successful result on one source does not establish that a fixed threshold or hard-coded value works elsewhere.
3. Practice the failing source, change the formula and check again. Unsupported attempts remain ungraded; opening help never completes a task.

• How practice is checked →
• Practice challenges →

A saved result and a formula recalculated by another spreadsheet app are different kinds of evidence.

1. The current-data download keeps the worksheet values and formulas. Freeze results removes formulas and preserves the displayed typed values.
2. Modern functions require a compatible client. A browser check or a cached XLSX result does not certify recalculation, editing or saving in native Excel or Sheets.
3. For a supplied native-only worked example, keep its recorded-source scope separate from an editable browser calculation.

• Our calculation and download boundaries →
• Native ETS worked examples →

A reference entry does not promise that every function, argument or external connection runs here.

1. Read the page’s practice status. A checked example, contextual practice, a saved native example and reference-only information have different coverage.
2. Follow the input contract for the selected task. An unsupported check has no overall pass/fail result.
3. A function that depends on an external service may require a native account, connection or add-in. This local helper does not create those bindings or contact a service.

• Function library and status →
• How calculations are checked →