Excel: "There are one or more circular references"
Hi, it's BlueByte. A circular reference warning sounds vague, but the fix is concrete: find the one cell that closes the loop and break it. Let's have Excel point you straight at that cell, fix it, and cover the one case where the loop is actually on purpose.
What the warning means
A warning appears and a cell shows 0 or a wrong result:
There are one or more circular references where a formula refers to its own
cell either directly or indirectly.Excel cannot compute a formula that depends on its own output, so it stops, warns you, and leaves the affected cells at 0 until you break the loop. The trick is finding exactly which cell closes the loop, because the warning names the workbook, not always the cell.
How a formula ends up referring to itself
A cell's formula includes its own cell in the calculation, one of two ways:
- Directly —
A1contains=A1+1, referring to itself. - Indirectly —
A1usesB1, andB1usesA1, so the two depend on each other through a chain, sometimes several cells long.
Each recalculation would change an input to itself, so there is no stable answer. Occasionally the loop is deliberate (some engineering or financial models iterate on purpose), but usually it is an accident from dragging a formula one cell too far.
Let Excel point you at the exact cell
You do not have to hunt for it. On the Formulas tab, open the Error Checking dropdown and point to Circular References — it lists the offending cell; click to jump there. The status bar also shows "Circular References:" with a cell address. Then use Trace Precedents (same tab) to see which cells feed the formula and where the loop closes — following the arrows back to the starting cell shows you the whole chain.
Break the loop (or allow it, if intended)
-
Go to the cell the Circular References list points at.
-
Rewrite the formula so it no longer depends on its own result — usually by pointing at a different input cell, or by splitting the calculation across two cells so nothing feeds itself.
-
If the loop is intentional, enable it deliberately: File → Options → Formulas → Enable iterative calculation, and set a sensible maximum iteration count and change threshold.
A real case: a SUM that summed itself
A running-total column suddenly shows 0 and the status bar reads "Circular References: D10". You go to D10 and see =SUM(D2:D10) — the total accidentally includes its own cell because the range was dragged one row too far. You change it to =SUM(D2:D9), the loop is gone, the warning clears, and the running total computes. Trace Precedents on D10 confirmed the loop pointed straight back at D10, which made the fix obvious.
Confirm the warning is gone
Recalculate (F9) and confirm the warning is gone and the cell shows the value you expect. Check the status bar — it should no longer read "Circular References". If a number still looks wrong, run Error Checking again in case a second loop exists on another sheet.
Keep it from recurring
Leave iterative calculation off unless a model genuinely needs it — with it on, Excel stops warning about circular references entirely, which hides accidental loops. Build formulas that read from inputs and write to separate outputs, never back into their own inputs, and double-check ranges after dragging a formula.
How this differs from #REF! and #VALUE!
A circular reference is a structural problem — the formula points at itself. That is different from #REF! (an invalid reference to a deleted cell) or #VALUE! (a wrong argument type): those are about what a formula references, not about it referencing itself. So when you see the circular-reference warning, look at the cell's own range first.
Related questions
The status bar shows 'Circular References' but no cell address.
The reference is on another open worksheet. Use Formulas → Error Checking → Circular References, which searches every sheet in the workbook.
Should I just turn on iterative calculation to make the warning go away?
Only if the loop is intentional. Turning it on to silence an accidental circular reference leaves you with a silently wrong number.
What is a safe iteration count if I do need it?
Start with the default (100 iterations, 0.001 change) and tighten only if your model needs more precision. Very high counts slow recalculation.
Why does my cell show 0?
When Excel detects a circular reference and iterative calculation is off, it cannot compute the cell and displays 0 until you break the loop.
It appeared after I dragged a formula down. Why?
Dragging can extend a range to include the formula's own cell — a SUM that now sums itself. Check the range in the cell the warning names and trim it back.
References
Haneul Seo
Infrastructure engineer · 10+ years running Linux fleets
More in this category
Gmail rejects your mail with 550-5.7.26: unauthenticated email is not accepted due to the domain's DMARC policy
Gmail enforced the DMARC policy your own domain publishes: the message failed both SPF and DKIM alignment against the header From: domain, so a p=quarantine or p=reject policy turned it into a hard bounce. The Authentication-Results header names the failing check, and three dig queries against your SPF, DMARC and DKIM records name the cause. A near-identical bounce about authenticating with SPF or DKIM is a different problem — Gmail's baseline sender requirements, not your policy.
Microsoft Entra ID: AADSTS50011, the redirect URI specified in the request does not match the redirect URIs configured for the application
Sign-in completes and then Entra ID refuses the last hop, because the redirect_uri your app sent is not a byte-for-byte match for any URI registered on the app. The match is case-sensitive, counts the trailing slash, requires https outside localhost, and treats the port as significant everywhere except localhost. It also splits by platform: web, spa and publicClient are three separate lists, and URIs added to the service principal instead of the application object can disappear. Read the URI and the app ID out of the error, compare them with az ad app show, add the exact string with az ad app update or a Graph PATCH, then wait three to five minutes.
Exchange Online: 535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled
A scanner, script or app that sends through smtp.office365.com gets 535 5.7.139 because the SMTP AUTH protocol is switched off for the tenant, for that mailbox, or by an authentication policy or security defaults that block Basic authentication. Read the wording (Tenant, Mailbox, or 'did not meet the criteria'), confirm with Get-TransportConfig, Get-CASMailbox and Get-AuthenticationPolicy, then open SMTP AUTH on the one mailbox that needs it rather than tenant-wide. Treat Basic SMTP AUTH as a bridge: Microsoft disables it by default for existing tenants at the end of December 2026, so move the sender to OAuth, High Volume Email or a relay connector.
Zoom: "Unable to connect" error code 5003 — the desktop app can't reach Zoom while the browser can
Error 5003 is the Zoom desktop app failing to complete its connection to Zoom's servers while the web client on the same machine joins fine. The app needs more than a browser does: Zoom's firewall article lists TCP 443/8801/8802 and UDP 3478/3479/8801–8810 for meetings, a set of CA hosts for certificate validation, and it asks that zoom.us and *.zoom.us be exempted from proxy or SSL inspection. A port test, a curl issuer check, and the app's built-in Network Connectivity Tool (Ctrl+Alt+Shift+D / Cmd+Option+Shift+D) show which of those is cut; fix that layer, and reinstall only when a single machine fails while its neighbours join.
Slack: "Slack cannot connect" and the grey "Last updated…" banner behind a corporate proxy
Slack loads channels over ordinary HTTPS but delivers new messages over a persistent WebSocket on port 443 to the three wss-*.slack.com hosts Slack names (primary, backup, mobile). When a proxy or firewall passes the HTTP side and blocks the upgrade — most often because SSL decryption is on for the wss hosts, or the allowlist stops at slack.com — the app shows the grey "Last updated…" banner or "Slack cannot connect." while the browser seems fine. Two curl probes from the affected machine show which layer is blocked; exempt the three wss hosts from decryption, allow every domain on my.slack.com/help/urls, and confirm with my.slack.com/help/test.
Word: "The document is locked for editing by another user"
Word found a lock — an owner file — for the document and assumed someone else has it open, so it offers only a read-only copy. Usually no one does: a crash left the lock behind, or a hidden Word process is still holding the file. Confirm which, close every Word instance, delete the stale ~$ owner file, and the document opens for editing again.