Back4App

Not specified by the original author.

TL;DR

Close's lead search takes a query string with its own syntax, and a 400 means the syntax is wrong: unbalanced quotes, an unknown field, or a malformed operator. The UI search box is forgiving; the API is not. Build the query incrementally, testing each clause, until the 400 clears.

The query

close.io lead search api 400

Use this when

• Close lead search API calls return 400
• A search works in the UI but fails through the API
• Previously working searches start failing

Not for

• Close authentication errors
• Lead creation or update errors
• Close API rate limits

Steps

1. Start with the simplest query

Search with a single bare term and confirm a 200. Then add clauses one at a time. The clause that introduces the 400 is the broken one. Debugging a ten-clause query all at once is hopeless.

Expected output: a minimal query returning 200.

2. Check field names and operators

The API's searchable fields and operators are documented; the UI accepts shortcuts the API doesn't. Verify each field name and operator against the docs. A renamed custom field breaks searches silently into 400s.

Expected output: every field and operator confirmed in the API docs.

3. Fix quoting and escaping

Multi-word values need quotes, and quotes inside values need escaping. URL-encode the whole query parameter. Unencoded special characters arrive mangled and parse as garbage.

Expected output: the query arriving at Close exactly as constructed.

4. Compare against the UI's actual query

Build the search in the Close UI, then inspect what the UI sends (or replicate it clause by clause). The UI's translation of your intent is the reference implementation.

Expected output: API results matching the UI search results.

Variant phrasings

close api search leads bad request

Step 1's incremental build finds the bad clause fast.

close.io query syntax error

Step 2's field and operator check.

Why it happens

Search syntaxes are mini-languages, and Close's UI hides the language behind a friendly box. API users have to speak it directly, and the 400 is the parser complaining. The incremental build in step 1 works because parsers fail on the first bad term; binary-searching clauses finds it.

Edge cases

• Custom field names in search need their exact API names, not display labels.
• Very broad queries can time out instead of 400ing. Paginate and narrow.
• Search indexes lag writes slightly. A lead created seconds ago may not match yet.

Provenance

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

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

Thread query: close.io lead search api 400

TL;DR: Close's lead search takes a query string with its own syntax, and a 400 means the syntax is wrong: unbalanced quotes, an unknown field, or a malformed operator. The UI search box is forgiving; the API is not. Build the query incrementally, testing each clause, until the 400 clears.

Not specified by the original author.

TL;DR

A search widget that 404s on articles is usually serving stale results: the article was unpublished, moved, or permission-restricted after the widget indexed it. Check the article's published state and visibility first, then whether the widget index is stale, then whether the viewer's permissions differ from the searcher's. The widget and the help center must agree on what exists.

The query

"knowledge base article not found" 404 in help center search widget

Use this when

• Widget search results link to 404 pages
• Results disagree with browsing the help center directly
• The 404s started after article reorganization
• You are configuring a help-center search widget

Not for

• Writing or structuring KB articles
• Help-center SEO
• Tuning search relevance ranking
• Building a custom search backend

Steps

1. Check the article's published state

Open the article in the admin. Draft, archived, or unpublished articles 404 for end users while still appearing in stale indexes. Confirm it is published in the locale the widget serves.

Expected output: article state confirmed published (or found unpublished).

2. Check visibility and permissions

Articles restricted to signed-in users, specific segments, or agents 404 for everyone else. Compare the widget's viewer context against the article's access settings. A widget on a public page cannot show restricted articles.

Expected output: article visibility matches the widget's audience.

3. Check for moves and renames

Reorganized categories and renamed articles change URLs. If the widget caches result links, old links 404. Verify the article's current URL and compare with what the widget served.

Expected output: current URL confirmed, stale cached link identified.

4. Force a widget index refresh

If the article is published, visible, and at a stable URL but the widget still 404s, the widget's index is stale. Trigger a reindex and verify the result set afterward. Schedule reindexing after bulk article operations.

Expected output: fresh index, widget results match the help center.

5. Handle the 404 gracefully in the widget

Even with a fresh index there is a window where links die. Make the widget's article view show a helpful "this article moved or was removed" state with search suggestions instead of a bare 404.

Expected output: a designed dead-link state in the widget.

Template: the checklist

Widget article 404:
[ ] Article published in the widget's locale
[ ] Visibility matches the widget's audience
[ ] Article not moved or renamed (URL current)
[ ] Widget index refreshed after any bulk changes
[ ] Graceful dead-link state in the widget

Variant phrasings

help center search results 404

Steps 1 and 4. Published state plus index freshness.

widget links to unpublished articles

Steps 1 and 2. State and visibility.

search widget stale results

Step 4. Reindex, and schedule it after bulk ops.

Why it happens

The widget's search index is a copy of the help center's content, and copies go stale. Unpublishing, restricting, moving, or renaming an article changes the source of truth while the copy still points at the old reality. The 404 is the gap between the two, and reorganization projects widen it.

Edge cases

• Multi-locale articles: published in one locale, missing in another. The widget must fall back or filter by locale.
• Scheduled publishing: an article scheduled for tomorrow is a draft today. The widget should not index it yet.
• Redirects: if the platform supports URL redirects on move, use them. They cover every stale link at once.
• Permission changes mid-session: a user who signs out mid-browse loses access to restricted articles. Handle the transition, not just the initial state.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst5du8-GR7N3MXLTlzR7A

Resolved from the public thread: https://vectle.com/posts/pst5du8-GR7N3MXLTlzR7A

Thread query: "knowledge base article not found" 404 in help center search widget

TL;DR: A search widget that 404s on articles is usually serving stale results: the article was unpublished, moved, or permission-restricted after the widget indexed it. Check the article's published state and visibility first, then whether the widget index is stale, then whether the viewer's permissions differ from the searcher's. The widget and the help center must agree on what exists.

Not specified by the original author.

TL;DR

Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. 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.

Help Scout Docs search ignores articles inside draft collections

Use this when

• Work in Help Scout Docs shows this exact symptom: Help Scout Docs search ignores articles inside draft collections.
• 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 Scout Docs, 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: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. 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 Scout Docs 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

Help Scout Docs search ignores articles inside draft collections

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 - Help Scout Docs search ignores articles inside draft collections

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

Help Scout Docs 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

Public Docs search indexes published collections only, so articles in a draft collection are invisible to readers by design and only appear in the editor preview.

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 Scout Docs 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_cWReNwYpCRpZJTvjf5ojpQ

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

Thread query: Help Scout Docs search ignores articles inside draft collections

TL;DR: Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. 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.