Diagnosing Stack Overflow Tag Synonym Issues: Cache, Duplicates, Locks, and Conflicts
A step-by-step diagnostic guide for Stack Overflow tag-synonym problems: cache delays, duplicate entries, locked tags, high-score conflicts, and stale UI, with checks, fixes, and when to escalate.
05 Feb 2026, 16:00 UTC

Recognizable condition
You have approved a tag synonym on Stack Overflow, but the old tag name still appears in posts, search suggestions, or the tag dropdown. This can happen for several reasons, ranging from simple UI caching to system-level restrictions.
Cause / diagnostic table
| Observed symptom | Likely cause |
|---|---|
| Synonym shows as “approved” but new questions still use the source tag | Search index or tag-suggestion cache has not refreshed yet |
| Two identical synonym entries (same source → target) appear in the synonyms page | Duplicate request submitted while the first was still pending |
| Synonym request is denied with a message about “tag locked” or “protected” | Target tag is protected (moderator-only) or has exceeded the usage threshold that blocks new synonyms |
| After approval, the old tag persists in the tag dropdown or autocomplete | Browser or site-wide CDN cache serving stale HTML/JS |
| Both source and target tags have high scores or are community-wiki, and the synonym behaves unpredictably | System avoids merging high-impact tags to preserve expertise signals |
Ordered checks
- Verify the synonym status
- Go to
https://stackoverflow.com/tags/source-tag/synonyms(replace source-tag with the actual tag). - Look for the entry
source-tag → target-tagand note its status (Pending, Approved, Denied).
Required permission: Any user can view the page; to see and vote on pending suggestions you need sufficient reputation on the tag.
- Go to
- Check recent posts for the source tag
- Run the search query
[source-tag]in the Stack Overflow search bar. - Inspect the tag list below the results; approved synonyms should cause the source tag to be displayed as the target tag name.
Tip: Add
is:qto limit results to questions if needed. - Run the search query
- Confirm cache freshness
- Open an incognito/private-browsing window and repeat the search from step 2.
- If the tag now appears as the target, the issue was a browser or CDN cache.
- Inspect tag history
- Visit
https://stackoverflow.com/tags/source-tag/infoand follow the history link. - Look for a synonym event with the correct source and target tags and a timestamp.
- Visit
- Check for lock or protection on the target tag
- Go to
https://stackoverflow.com/tags/target-tag/info. - If the tag is moderator-managed or marked protected, only moderators can change its synonyms.
- High-usage tags (e.g.,
java,javascript) have internal thresholds that can block new synonyms; the denial message will reference this.
- Go to
Fixes tied to findings
1. Cache refresh delay
If the synonym is approved but posts still show the source tag:
- Wait a short while for the background search index to update; tag changes are not always instantaneous.
- Force a UI refresh: hard-reload the page (Ctrl+Shift+R) or use an incognito window.
- After waiting, repeat the search from step 2 of the checks to confirm the target tag now appears.
2. Duplicate synonym entries
When you see two identical source→target lines:
- Navigate to the synonyms page for the source tag.
- If you have the privilege to manage synonyms, remove the duplicate entry.
- If you lack the privilege, raise the issue on Meta Stack Overflow or flag for moderator attention.
3. Target tag locked or protected
When the request is denied:
- Verify lock status as described in step 5 of the checks.
- If the tag is protected, only moderators can add synonyms; request the change via a Meta post explaining the rationale.
- If the denial cites a usage threshold, consider proposing a synonym for a less-used variant of the tag instead.
4. Synonym conflict with high-score or community-wiki tags
When both tags are high-impact:
- The system may block the merge to preserve signal quality and tag granularity.
- Check each tag’s question count and activity on its info page before proposing the merge.
- If both tags are very large, consider alternatives:
- Keep the existing tags and rely on search filters to cross-reference them.
- Propose a new, more specific tag that captures the nuance without merging the high-impact ones.
5. Stale tag dropdown after approval
If the autocomplete still shows the old name:
- Clear the browser cache for stackoverflow.com (browser settings → privacy → clear browsing data → cached images and files).
- Alternatively, open developer tools (F12) → Application → Clear storage → “Clear site data”.
- Retype the tag in the ask-question field; the suggestion should now reflect the target tag.
Escalation criteria
Escalate to a moderator or raise a Meta post when:
- The synonym remains denied after verifying that the target tag is not locked, protected, or over the usage threshold, and you have sufficient reputation to suggest it.
- Duplicate synonym entries persist despite your attempts to remove them, indicating a possible bug.
- Approved synonyms are not applied to new posts after an extended wait and cache clearing, suggesting a problem with the background index job.
- A synonym merge collapses specialized tags and reduces discoverability; moderators can review and revert the change.
When escalating, provide:
- Exact source and target tag names.
- Links to the synonyms page and tag history.
- Screenshots showing the stale UI or duplicate entries, if possible.
- Any error messages received during the request.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.