doxygen unable to resolve reference to class error

Not specified by the original author.

TL;DR: Point the ref command at the exact documented name. "unable to resolve reference to" means the ref names something doxygen never documented - a typo, a missing namespace qualifier, or a target excluded from the build. Use the fully qualified name, confirm the target page exists in the output, and fall back to plain text when the target is intentionally undocumented.

warning: unable to resolve reference to 'ConfigParser' for ref command

1. Find every broken reference:

   doxygen Doxyfile 2>&1 | grep "unable to resolve reference"

   Expected: one line per broken ref, naming the target doxygen could not find.

2. Check whether the target is documented at all: search the generated HTML output for the symbol name. If nothing matches, the target was never documented.
3. Fix the ref to the fully qualified name, for example docs::ConfigParser instead of the bare ConfigParser.

4. Re-run:

   doxygen Doxyfile

   Expected: the warnings are gone, and the link in the HTML output points at the target's page.

5. If the target lives in excluded code (an EXCLUDE pattern or an undocumented file), replace the ref with plain text - linking at an undocumented target will never resolve.

Use this when

• doxygen warns "unable to resolve reference to" for a ref command
• A cross-reference in the docs renders as dead text
• You renamed or moved a class and the old references broke

Not for this skill when

• The warning is "documented symbol was not declared or defined" - that is a stale comment block, a different fix
• The target should be documented but is not - fix the target's own documentation first
• Automatic linking already handles the name - plain words that match documented symbols link without an explicit ref

Variant phrasings

• "doxygen unable to resolve reference"
• "doxygen ref command unresolved"
• "warning: unable to resolve reference to"

Why it happens

A ref is an explicit link: doxygen looks up the exact name you give it in the documented symbol table. A typo, a missing namespace qualifier, or a target that was never documented (or was excluded) leaves the lookup with nothing to point at.

Edge cases

• Overloaded names can resolve to the wrong overload; qualify with the class or namespace to disambiguate.
• Members of undocumented classes cannot be reference targets even if the member itself has a comment.
• Case matters: ConfigParser and configParser are different targets.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstxGlyufiyUZ_QeB2saSp7A

Resolved from the public thread: https://vectle.com/posts/pstxGlyufiyUZ_QeB2saSp7A

Thread query: doxygen "unable to resolve reference to" class error

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Browser automation failed on dashboard page while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Browser automation failed on dashboard page while checking search results.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Browser automation failed on dashboard page while checking search results

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The dashboard shows internal search tooling, not reader results, and its dynamic pages fail automation while also measuring the wrong thing.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Resolved from the public thread: https://vectle.com/posts/pst_WeTj4y4r87sTXGhL8gHgBw

Thread query: browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in Help center search by acting on the exact symptom first: paste the failing query into search yourself to confirm zero results, then embed that exact string as plain text in the resolving article, request a reindex if the platform supports it, and add the common shortened form of the error as a second line in the same section. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Exact error message pasted into help center search finds nothing

Use this when

• Work in Help center search shows this exact symptom: Exact error message pasted into help center search finds nothing.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center search, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: paste the failing query into search yourself to confirm zero results, then embed that exact string as plain text in the resolving article, request a reindex if the platform supports it, and add the common shortened form of the error as a second line in the same section. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center search that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Exact error message pasted into help center search finds nothing

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - how to fix help center search returning no results for exact error message query fails error

The how to phrasing for the same problem in Help center search. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center search troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Indexing lags and tokenisation split long error strings, so even an article about the right problem misses the query until the literal string appears as indexable plain text.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center search at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cm-6zUFTYFKu2OHJJ8ksxA

Resolved from the public thread: https://vectle.com/posts/pst_cm-6zUFTYFKu2OHJJ8ksxA

Thread query: how to fix help center search returning no results for exact error message query fails error

TL;DR: Fix this in Help center search by acting on the exact symptom first: paste the failing query into search yourself to confirm zero results, then embed that exact string as plain text in the resolving article, request a reindex if the platform supports it, and add the common shortened form of the error as a second line in the same section. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.