healthcheck

Not specified by the original author.

TL;DR

[jdorn (maintainer)]: To healthcheck GrowthBook itself, hit the API server's GET /healthcheck endpoint (see the Self-hosting CDN docs). The GrowthBook Proxy exposes a /healthcheck endpoint too.

Steps

1. [jdorn (maintainer)]: To healthcheck GrowthBook itself, hit the API server's GET /healthcheck endpoint (see the Self-hosting CDN docs).
2. The GrowthBook Proxy exposes a /healthcheck endpoint too.

When to use

You are seeing this: GrowthBook - How can I connect healthcheck to get growthbook work status? Use this skill when you run into "How I can give a current status of growthbook (healthchecks)?".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/growthbook/growthbook/issues/2238

In gh:growthbook/growthbook#2238 (https://github.com/growthbook/growthbook/issues/2238), the issue reported: How can I connect healthcheck to get growthbook work status?

There is a healthcheck for growthbook-proxy (YOUR_HOST:3300/healthcheck - https://docs.growthbook.io/self-host/proxy), but I couldn’t find one for growthbook.

Please tell me how can I get the status of growthbook itself?

Thanks for the heads up in advance. The verified answer: [jdorn (maintainer)]: To healthcheck GrowthBook itself, hit the API server's GET /healthcheck endpoint (see the Self-hosting CDN docs). The GrowthBook Proxy exposes a /healthcheck endpoint too.

Not specified by the original author.

ombud answer library search returns no results error: how to fix it

Zero-result search with a populated library means the search index is empty or out of date. Check the index status in admin settings, force a reindex, and wait for it to complete before testing. Also confirm the search scope is not restricted to an empty collection.

ombud answer library search returns no results error

When to use this skill

• Search returns nothing while answers exist in the library
• Index timestamp is days older than the newest answer

When not to use this skill

• Some answers appear but others are missing (a partial index)
• Search returns others answers that belong to a different library (a permission scope)

Tool compatibility

Ombud answer library search and indexing. Related area: search and knowledge tooling.

Related area: proposal automation and agent-assisted RFP workflows.

Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with search returns nothing while answers exist in the library, start at step 1 below.
• If instead some answers appear but others are missing (a partial index), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Check the search index status

Open admin settings and find the search index status line.

Expected: Expected: status reads indexed with a recent timestamp, or flags that indexing never ran.

2. Force a reindex

Start a full reindex from the admin panel and leave the tab open.

Expected: Expected: progress indicator moves; completion message appears.

3. Widen the search scope

Set the search scope to all collections instead of one collection.

Expected: Expected: the same query now returns results.

4. Test with an exact answer title

Search for an answer title word for word.

Expected: Expected: that answer appears as the top result.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (check the search index status): Expected: expected: status reads indexed with a recent timestamp, or flags that indexing never ran.
• Step 2 (force a reindex): Expected: expected: progress indicator moves; completion message appears.
• Step 3 (widen the search scope): Expected: expected: the same query now returns results.
• Step 4 (test with an exact answer title): Expected: expected: that answer appears as the top result.

Quick recap

1. Check the search index status
2. Force a reindex
3. Widen the search scope
4. Test with an exact answer title

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

ombud search no results

Reindex plus scope check is the fix. If this matches what you saw, the steps above apply as written.

ombud library search broken

Empty or stale index is the cause. If this matches what you saw, the steps above apply as written.

Why it happens

Search reads from a prebuilt index, not the live library, so answers saved after the last index build are invisible to it. An index that never built in the first place returns zero results for everything.

Edge cases

• Reindexing on a huge library can take an hour; schedule it off peak
• Collection-scoped search hides answers silently; default new users to all collections
• A stuck index job usually needs a support ticket; note the job id from the status page

Provenance

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

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

Thread query: ombud answer library search returns no results error

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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.

Agent failed to check help center search results for an error query - timeout

Use this when

• Work in Search check agent shows this exact symptom: Agent failed to check help center search results for an error query - timeout.
• 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: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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

Agent failed to check help center search results for an error query - timeout

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 - agent failed to check help center search results for an error query error failure timeout

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

Batch checking dozens of queries in one step couples the whole check to the slowest query, and no per query verdict survives the timeout.

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_6dFD2l0g4rmnMOZDucfqFw

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

Thread query: agent failed to check help center search results for an error query error failure timeout

TL;DR: Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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.