Excel Errors and Troubleshooting Examples | The Excel Guide

Most people assume Excel errors mean their formula is wrong. That assumption is wrong about half the time, and it sends you chasing the wrong fix. After nearly two decades of daily Excel work, the most common pattern I see is a structurally correct formula failing because of bad data sitting quietly in a cell two columns over. Understanding that distinction is what separates someone who debugs fast from someone who rewrites formulas for an hour and ends up in the same place. This guide covers both formula errors and operational issues — the kind that have nothing to do with formulas at all — because the full picture of Excel errors and troubleshooting is wider than most guides admit.

The goal here isn't to hand you a list of error codes. It's to give you a repeatable process so that the next time Excel throws something unexpected at you, you know exactly where to look first.

Why Excel errors feel random (and why they're not)

Excel errors aren't random. They're literal. Every error code is Excel telling you exactly what went wrong — if you know the language. The problem is that most beginners skip past the code and immediately start editing, which is like getting a check engine light and opening the hood without a diagnostic tool. The code is the diagnostic tool. Start there.

The diagnostic habit that makes every fix faster

Before you change a single character in a formula, read the error value in the cell. Then hover over it — Excel will show a small tooltip explaining the issue. That two-second step eliminates most of the guesswork from spreadsheet troubleshooting. I built this habit after breaking a formula in front of senior management years ago. A colleague spotted mid-presentation that my formula failed on blank cells, an edge case I hadn't tested. The fix took thirty seconds. The lesson lasted a lot longer.

---

Step 1: Read the Error Code Before You Change Anything

Once you've accepted that the error code is information rather than an accusation, the next step is knowing what each code actually means. Excel uses seven formula error values, and each one tells you something specific about where the formula broke down.

The seven formula error values and what each one is actually telling you

Here's a plain-language breakdown of each Excel formula error you're likely to encounter:

How to use Excel's error checking tools to surface problems you can't see

Excel has built-in error checking tools that most people ignore. Go to Formulas → Error Checking to step through every flagged error in the sheet sequentially. The Trace Precedents button in the Formula Auditing section draws arrows directly to every cell your formula depends on, which makes it easy to spot when a reference has drifted somewhere unexpected. If you're debugging a complex model, these tools will find problems that visual scanning won't. They're especially useful when the same error has cascaded across a hundred rows and you need to identify where it originated.

For a broader overview of how formulas work before errors enter the picture, the Excel Formulas and Functions for Beginners guide is a solid starting point.

---

Step 2: Fix Formula Errors Using the Right Method for Each One

Reading the error code tells you what happened. Now you need to fix it — and the right approach depends entirely on which error you're looking at. Here are the specific fixes for the errors beginners hit most often.

Fixing #REF! after copying a formula and #VALUE! from mixed data types

A #REF! error after copying a formula almost always means a relative reference shifted somewhere invalid. If cell C2 contains =A2-B2 and you delete column A, Excel has nowhere to point for that first reference. Use Ctrl+Z immediately if the deletion just happened. If you needed to delete the column, rewrite the formula with the correct new reference. To prevent this in the future, use absolute references ($A$2) when the formula should always point to one specific cell regardless of where you copy it.

A #VALUE! error usually means a number column has text hiding in it, often from a CSV import or a copy-paste from another system. Select the column, go to Data → Text to Columns, finish the wizard without changing anything, and Excel will re-evaluate the cell types. If a single cell is the problem, check whether it contains a space or an apostrophe before the number.

Resolving circular reference errors without breaking your calculation logic

A circular reference happens when a formula refers back to its own cell, directly or through a chain of references. Excel will warn you when this occurs, and the cell will typically display 0. Go to Formulas → Error Checking → Circular References and Excel will show you exactly which cell is the source. In most cases, a circular reference is a structural mistake: a formula meant to reference one row above that accidentally points to itself. Fix the reference. If you genuinely need iterative calculation (rare, but it happens in financial models), you can enable it under File → Options → Formulas — but that's an edge case, not a default solution.

Handling the #SPILL! error in Excel 365 and Excel 2021

The #SPILL! error is specific to dynamic array functions in Excel 365 and Excel 2021, including FILTER, UNIQUE, SORT, and SEQUENCE. These functions return results across multiple cells automatically. If any cell in that output range is already occupied, Excel can't write the results and throws #SPILL! instead. Clear the cells in the spill range, or move the formula somewhere with enough empty space to expand into. Click the formula cell and Excel will show a blue border around the expected spill range so you can see exactly what's blocked.

The #SPILL! error only exists in Excel 365 and Excel 2021. If you're on an older version and see unexpected behavior from FILTER or SORT, those functions may not be available at all — not a spill issue.

---

Step 3: Use IFERROR, IFNA, and ISERROR as a Toolkit, Not a Patch

With your formula actually working correctly, you can think about how to handle errors that are expected — like a VLOOKUP that won't always find a match. This is where IFERROR, IFNA, and ISERROR come in. Most guides treat these as interchangeable. They're not.

When to use IFERROR vs. IFNA and why the difference matters

IFERROR catches every error type: not just #N/A but also #VALUE!, #REF!, #DIV/0!, all of them. That sounds convenient, but it's a trap if your formula has a genuine structural mistake. IFERROR will hide it. You'll see a blank cell or a zero and assume everything is fine while your data is quietly wrong.

Think of IFERROR as a finishing tool, not a debugging tool. Get the formula working correctly first. Then — and only then — wrap it.

IFNA is the more precise choice for lookup functions. It catches only #N/A errors and lets everything else surface visibly. So if your VLOOKUP has a #REF! because someone deleted a column in your reference table, IFNA won't hide it. That's the behavior you want. Use IFNA with VLOOKUP and XLOOKUP by default. Reserve IFERROR for situations where you've confirmed the formula is correct and want to suppress all error types intentionally.

Using ISERROR to test before committing, not after the fact

ISERROR returns TRUE or FALSE — it doesn't replace the error, it detects it. This makes it useful inside IF statements when you want to take different actions depending on whether an error exists. For example: =IF(ISERROR(VLOOKUP(A2,Table,2,0)),"Not found",VLOOKUP(A2,Table,2,0)). It's more verbose than IFNA, but it gives you full control over what happens in both the error and non-error case. In 2026, with XLOOKUP widely available, most of this complexity is unnecessary — XLOOKUP has a built-in if-not-found argument that handles it more cleanly. But ISERROR still has a place in legacy files and older versions of Microsoft 365.

---

Step 4: Troubleshoot Excel Problems That Have Nothing to Do with Formulas

Formula errors get all the attention, but some of the most frustrating Excel problems don't produce an error code at all. They just make the file slow, unstable, or wrong in ways that are hard to pin down.

Diagnosing slow calculation and performance issues

If Excel is running slowly, volatile functions are the first thing to check. INDIRECT, OFFSET, NOW, TODAY, and RAND recalculate every time anything in the workbook changes, including when you type in an unrelated cell. A few of these are fine. Hundreds of them in a large model will grind calculation to a halt. Replace INDIRECT and OFFSET with non-volatile alternatives where possible, and consider switching to manual calculation mode (Formulas → Calculation Options → Manual) while working on large files.

Excessive conditional formatting is another common culprit, especially formatting applied to entire columns rather than specific ranges. Check Home → Conditional Formatting → Manage Rules and look for rules applied to columns A:A or 1:1048576. Those cover over a million cells. Trim them to the actual data range and you'll often see an immediate performance improvement. These same issues show up constantly in Excel financial models, where ranges tend to grow large and volatile functions accumulate over time.

Good Excel file management practices, including keeping file sizes reasonable and avoiding unnecessary formatting, prevent most of these problems before they start.

What to do when Excel crashes or a file won't open correctly

If a file won't open, try File → Open → Browse, select the file, click the dropdown arrow on the Open button, and choose Open and Repair. This is Excel's built-in recovery tool and it works more often than people expect.

CSV import errors are a separate category. When you open a CSV directly in Excel, it makes automatic decisions about data types — and it gets them wrong regularly. Phone numbers lose their leading zeros. Dates reformat themselves. Long numeric strings get converted to scientific notation. The fix is to import via Data → Get Data → From Text/CSV in Power Query, where you can set column types manually before the data ever hits the sheet. If your data looks wrong after a CSV import and you don't see an error code, this is almost certainly what happened.

---

The Most Common Excel Troubleshooting Mistakes (Including the One That Hides the Problem)

The single most common mistake I see from beginners: wrapping a broken formula in IFERROR before understanding what broke it. The formula returns something. It looks fine. It isn't. Silent wrong data is worse than a visible error code.

The second mistake is deleting and retyping formulas instead of using formula auditing. Retyping feels productive. It rarely fixes anything unless you happen to accidentally correct the real problem while you're in there. Use Trace Precedents. Use the error checker. Find the source before you touch anything.

A third pattern I see constantly: finding the fix for an error in one cell and stopping there. If the formula is copied across 200 rows, the same structural issue exists in every one of those rows. Fix the source, then propagate the correction. Don't patch cell by cell.

Finally, check your Excel version before following troubleshooting advice from an article. #SPILL! errors, dynamic array behavior, and XLOOKUP availability are all version-dependent. A fix written for Excel 365 may not apply to Excel 2019, and vice versa. If you're newer to Excel generally, the Excel for Beginners starter guide covers the version landscape alongside the fundamentals. And if you want to build the kind of data entry habits that prevent half of these errors before they happen, data entry and formatting in Excel is where that starts.

---

---

Frequently Asked Questions