Gnumeric Calculation Error Reference
Choose a targeted Gnumeric error investigation with controlled examples and explicit verification limits.
Scope: Gnumeric desktop, English 1.12-series manual checked October 21, 2026. Distribution builds and translations may differ. These new exercises have not been executed in Gnumeric; results below are documentation-supported expectations and independently checked arithmetic or logic, not native test observations. Work in a disposable workbook, not your original.
Choose the investigation, not a blanket fallback
These references cover selected documented calculation-error families. They are not a complete catalogue of every failure, file-format issue or version-specific behavior. Read the actual formula before choosing a branch.
-
#DIV/0!: inspect the divisor: A percentage or unit rate has a zero baseline.
-
#NUM!: inspect the mathematical domain: The input is numeric, but outside the operation’s permitted domain.
-
#REF!: inspect geometry and address style: A requested range position or text address is invalid.
-
#VALUE!: inspect the argument contract: A checklist has no usable logical inputs or another argument is invalid.
-
Circular dependencies and self-including totals: Separate an accidental impossible total from an intentional model that needs explicit assumptions and residual checks.
Capture enough evidence to verify a repair
Keep the original workbook unchanged. In a separate copy, record the exact error, formula, direct inputs and expected meaning of the result. Test one ordinary input, one boundary and one intentionally invalid input. A displayed number is not proof that a repaired formula references the correct data.
The worked exercises use harmless synthetic values. Their expectations are not screenshots or fresh execution results. Check the scope on each reference before applying it to your installed build, and do not extend a documented example into a claim about every platform.
An error handler is a reporting decision, not a diagnosis. A zero fallback can conceal an unavailable amount or broken dependency. Keep exceptional records visible until their cause and intended treatment are understood.
For symptoms other than these selected errors, start with general troubleshooting. For a particular function’s complete arguments, use the function guides.