Feature Errors

Formulas can be perfect and the numbers still wrong — because a feature failed. Power Query didn't refresh. A PivotTable's source range shifted. A chart references a range that no longer exists. Data validation stopped catching bad inputs. These aren't hash errors and there's no #ERROR to alert you — the feature just fails silently or displays a dialog you dismiss without reading. This page tells you what those dialogs actually mean.

The four you'll see most

Browse feature errors by area

The single most important prevention pattern

Convert all your data ranges to Excel Tables (Ctrl+T). Tables automatically:

• Expand as you add rows — PivotTables, charts, and Power Query queries following the table auto-adjust
• Retain formatting and validation on new rows — data validation extends automatically
• Provide structured references — formulas use column names, not fragile A1 addresses
• Prevent most "source changed" errors — the source is a Table with a fixed name, so refresh operations always find it

About 40% of the errors on this page never happen if you use Tables. Highest ROI Excel habit you can adopt.

Diagnostic flow — feature stopped working, where do I look?

1. Read the actual error dialog carefully. Excel usually names the specific cause. Dismissing without reading is why users repeatedly hit the same issue.
2. For Power Query: open Query Editor (Data → Queries → double-click query) → look at Applied Steps → the first step showing an error is the failure point.
3. For PivotTable: PivotTable Analyze → Options → Data → note the source range. Verify it still exists and includes all current data.
4. For Charts: right-click → Select Data → check each series reference. Broken references show as #REF! or empty.
5. For Conditional Formatting: Home → Conditional Formatting → Manage Rules → check "Applies to" ranges are still valid.
6. Use Formulas → Trace Precedents for any single cell to see what it depends on. Often reveals the broken link.

Prevention patterns

• Use Tables for all source data (already covered — worth repeating)
• Use named ranges for stable references: if a chart references a named range instead of hardcoded cells, moving data doesn't break it
• Test after adding new rows: add a row → refresh Pivot → check chart → verify conditional formatting still applies
• Document Power Query source paths: keep a Notes sheet listing what queries pull from where
• Refresh regularly, not just occasionally: failures are easier to diagnose when they happen soon after the source change
• Turn on background refresh for Power Query: Query Properties → refresh in background → catches problems as they happen

Frequently asked questions