ERRORTYPE in Zoho Sheet: Spreadsheet Error Codes and Diagnostics

When an imported dataset or calculated report displays multiple errors, ERRORTYPE helps turn a known error in a specific cell into a numeric category. This can make it easier to classify a broken source reference separately from division by zero, an invalid name, a numeric calculation problem, or genuinely missing data. It does not fix the underlying formula or explain why the error occurred: use it to diagnose, then inspect the original formula and inputs.

The most important trap is that a normal cell does not produce “0” or “no error” as a numeric output. Zoho states that a no-error reference produces #N/A!. At the same time, an actual circular-reference error is explicitly code 0. Therefore a zero, if reported under Zoho’s mapping, is not a success indicator. Official Zoho mapping.

=ERRORTYPE(reference)

Zoho shows a single required reference. It does not document an omitted-argument default, nor a special mode for a whole multi-cell selection. To diagnose a column, put one ERRORTYPE formula beside each source cell and fill it down; do not assume that supplying a multirow array to this function returns a vector of codes. Formula spelling is exactly ERRORTYPE (without a dot) in Zoho’s English Help, rather than Excel’s related ERROR.TYPE spelling. Zoho ERRORTYPE.

Zoho’s complete documented code table

The spellings are transcribed as Zoho documents them, including #NULL, #NUM, #N/A! and #CIRCULARREF!. Do not silently rewrite them into another application’s display conventions or assume all regions visually render them identically. Zoho does not list a separate return code for every imaginable plugin or application-specific failure. Official ERRORTYPE error-code table.

Create a worksheet called Error Audit. Enter the following formulas; these are ordinary illustrative sources, not a claim that Zoho’s live service has been tested here:

Enter =ERRORTYPE(A2) into B2, similarly using A3, A4, A5 in the following cells. Based on Zoho’s documented mapping and the stated source conditions, the expected outputs are:

You can perform the documented vendor-reference checks separately: =ERRORTYPE(A4) → 3 only in Zoho’s own example workbook where A4 contains the error of that class; do not confuse that official A4 with the A4 cell in this new practice workbook. Context matters. Zoho example and code table; Zoho NA.

Demonstrating other errors without fragile recipes

For #REF!, #NAME!, and #VALUE!, prefer to paste a confirmed error value into a test workbook or inspect an existing genuinely failing formula, and then use a neighbouring ERRORTYPE reference. Deleting a source column or constructing a malformed formula can affect a workbook in ways that complicate reproducibility. The expected codes are 4, 5 and 3 conditional on the source cell truly containing those errors. A missing name may be rejected at input time rather than evaluate as a stored error on some interfaces; that behaviour is not established here.

For code 0, do not deliberately set up recursive calculations in a production sheet. Circular-reference detection or iterative-calculation settings can be account/workbook-specific. Zoho lists the code, but we have not observed that error in a signed-in workbook. Similarly, do not promise a direct formula recipe for #NULL or #NUM without native evidence.

ERRORTYPE classifies an error; ISERROR merely reports whether an error is present; ISNA narrows the question to missing values; ISERR detects errors except #N/A!. Zoho documents all three tests independently. Consider a product-price lookup:

• Use ISNA(A3) when a genuinely missing product is an anticipated state that the report should treat differently.
• Use ISERR(A3) when broken arithmetic, invalid names or bad references should be escalated as data-quality defects rather than hidden.
• Use ISERROR(A3) to identify any error type; this may also be TRUE for intentionally missing data.
• Use ERRORTYPE(A3) to attach the documented numeric code after confirming an error exists.

These are different purposes. Suppressing every problem with a generic fallback can hide a broken workbook, so reserve global error fallbacks for contexts where loss of diagnostic visibility is acceptable. Zoho ISNA; ISERR; ISERROR.

A robust conceptual error-audit design uses one helper column for =ISERROR(A2) and another for =ERRORTYPE(A2) only in rows where the error flag is TRUE. This avoids pretending a normal cell should have a code. If you implement this with an IF wrapper, verify the target Zoho formula evaluator’s conditional evaluation; the vendor’s ERRORTYPE page does not explicitly guarantee short-circuit semantics for expressions it encloses.

A proposed formula using Zoho’s documented semicolon-style examples is:

=IF(ISERROR(A2);ERRORTYPE(A2);"No error")

Expected by independent boolean and conditional reasoning: for source =1/0, 2; for source =NA(), 7; for source =25, No error. The composition is useful, but has not been executed in Zoho Sheet; if evaluation of an unused branch differs in a given edition, use two simple helper columns to avoid relying on branch laziness. The official ERRORTYPE page documents its numeric codes, and Zoho documents ISERROR separately. Zoho ISERROR; Zoho IF.

If your file contains a planned missing-value marker from NA(), an ERRORTYPE result of 7 means the source cell is an actual unavailable-value error, not necessarily that a query to another system has failed. An IFNA wrapper can display a more legible message for #N/A specifically, without treating a broken reference as a normal missing value:

=IFNA(A3;"Missing product")

Under the source condition A3=NA(), the vendor-documented IFNA concept yields the text Missing product. Its specific syntax is validated by Zoho’s IFNA documentation; this guide is not a native execution report. For an actual #REF!, IFNA is not intended as an all-errors fallback. Diagnose the source instead. Zoho IFNA; Zoho ERRORTYPE.

Zoho lists #N/A!, #NAME!, #VALUE! and #REF! under possible errors for this function. The first two columns above distinguish a numeric code returned because of a source error from an error raised by the ERRORTYPE call itself; their appearance can look similar until you inspect where the formula actually failed. Official ERRORTYPE error list.

Cross-program naming: Excel documentation calls a comparable function ERROR.TYPE; Zoho’s documented identifier is ERRORTYPE. Directly pasting formulas between spreadsheet programs may require a function-name rewrite. Do not assume their error codes, special error spellings, number of error categories, or error-propagation behavior are interchangeable. We did not import a workbook into Excel or Zoho, and this comparison is based on published vendor materials only. Zoho ERRORTYPE; Microsoft ERROR.TYPE.

Zoho’s current public English Help is a cloud-service documentation source; it does not provide a function-specific minimum version, old desktop edition matrix, full mobile parity table, or plan-tier availability guarantee. We therefore do not claim an invented date of introduction, guaranteed offline execution, or a regional difference. ERRORTYPE alone takes one argument, so argument separators are immaterial until you combine it with another function such as IF or IFNA; review the current editor’s locale settings and published formula examples for semicolon/comma usage. Zoho locale settings.

• ISERROR — determine whether a value is any kind of error.
• ISERR — errors except #N/A!.
• ISNA — only #N/A!.
• NA — deliberately generate an unavailable-value marker.
• IFNA — supply a fallback only for the unavailable-value case.

These links point to the corresponding official vendor documentation.

• Syntax, one required reference, eight error-category mappings, no-error result, official A4/A8 examples and possible error descriptions: Zoho Help — ERRORTYPE, checked 2026-10-13.
• Producing a true unavailable-value error: Zoho Help — NA, checked 2026-10-13.
• Classifying any error / excluding unavailable / detecting unavailable: ISERROR, ISERR, and ISNA, all checked 2026-10-13.
• Handling only #N/A: IFNA, checked 2026-10-13.
• Cross-application spelling reference: Microsoft ERROR.TYPE documentation, consulted 2026-10-13 for comparison only.
• Verification boundary: all sample outputs are derived from Zoho’s published mapping and basic independent reasoning. Zero native Zoho Sheet executions, no signed-in application screenshot, edition matrix, or supported-since-version test.