health pulse

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.

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.

Not specified by the original author.

TL;DR

InvalidBatch tells you the job container was fine and one batch inside it was not, so stop restarting the whole sync and go batch hunting. Open the Bulk API job, read the failed batchs own error, and you will usually find a malformed SOQL query, a CSV payload problem, or an unsupported operation in that batch alone. Fix that batch, resubmit only the failed portion, and the health fields land without a risky full reload.

Salesforce Bulk API InvalidBatch failed to process query when syncing account health fields to the CRM

Use this when

• A Salesforce Bulk API job completes with failed batches in InvalidBatch state
• Some account health fields updated and others are stale from the same run
• The same sync worked at smaller volume or with a narrower query

Not for this skill when

• Every batch fails identically from the job creation step, which points at authentication or API version instead
• Single record updates through the UI also fail, suggesting validation rules rather than bulk formatting

Steps

1. Retrieve the job and its batch list through the Bulk API or your integration tool, and capture the state message for each InvalidBatch batch rather than the jobs summary line. The batch-level message names the real problem, such as a malformed query, an invalid field, or a formatting error in the records payload. Verify: the failing batches and their individual messages are listed
2. If the failing batch is a query batch, take its SOQL into Salesforce Workbench or the query editor and run it there unchanged. Bulk query rejects some constructs that interactive SOQL tolerates, including certain aggregate and date literal patterns, and a field renamed in the org breaks every batch that selects it. Fix the query to the Bulk-supported shape and confirm it returns rows in the test. Verify: the corrected query executes in the test tool and returns the expected account set
3. If the failing batch is an update batch, inspect its payload file around the reported row. Common killers are unescaped commas and quotes in CSV, a health score sent as text with locale decimal separators, empty strings sent for numeric fields instead of null markers, and external id values containing characters that break the file structure. Regenerate the payload with a real CSV writer and explicit null handling. Verify: the regenerated payload passes a local parse and row count check matching the source extract
4. Check field level reality in the org. Confirm the health fields exist in this org, the integration profile can edit them, and no new validation rule or duplicate rule rejects the values the sync sends, for example a rule demanding a score reason whenever the score changes. Test one record update through the REST API with the same payload values to surface org-side rejections in plain language. Verify: a single record updates cleanly with the same values, or the org rule blocking it is named
5. Resubmit only the failed batches as a new job, keep the successful batches out of it, and reconcile by counting accounts whose health fields carry todays sync timestamp against the source extract count. Reconcile on counts and samples, not on job status alone. Verify: resubmitted batches complete and the reconciled account count matches the source
6. Harden the sync. Validate payloads against the org schema before submission, split batches by operation and segment so one bad shape cannot poison a whole run, and alert on any batch ending in a failed state with its message attached to the alert so the next occurrence arrives pre-diagnosed. Verify: the pre-flight validation and batch state alert are in place and tested with a deliberately bad batch

Why it happens

A bulk job is a set of independent batches, and Salesforce marks a batch InvalidBatch when its own content cannot be processed, while sibling batches succeed. Integrations that only watch job status either miss the partial failure or retry the entire load, duplicating updates and still failing on the same bad batch. Partial staleness in the health fields is the visible symptom of that one poisoned batch being skipped run after run.

Compatibility: Salesforce Bulk API 1.0 and 2.0 job and batch model, Workbench query testing, and current Salesforce org validation and profile controls.

Variants and edge cases

Salesforce Bulk API InvalidBatch state message meaning

['The meaning-first phrasing. InvalidBatch is a batch-level verdict, so always drill to the batch state message before changing job level settings.']

bulk query batch failed health sync Salesforce

['The query-batch variant. Reproduce the SOQL outside the integration first, it is the fastest way to separate query problems from payload problems.']

bulk update CSV batch invalid account health fields

['The payload variant, usually escaping or type formatting. Diff a failing row against a succeeding row from the same file to spot the pattern quickly.']

Edge cases to work through before you close the incident:

• Bulk API 1.0 and 2.0 differ in how jobs, batches, and errors surface. Confirm which version your integration uses before following menu paths or endpoint shapes.
• Hard delete and some operations need special permissions and behave differently in batches. Keep operation types in separate jobs so their failures stay legible.
• External id fields with case-sensitive values can match a different record than intended. Sample-check updated records by account name, not only by counts.

Provenance

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

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

Thread query: Salesforce Bulk API InvalidBatch failed to process query when syncing account health fields to the CRM

TL;DR: InvalidBatch tells you the job container was fine and one batch inside it was not, so stop restarting the whole sync and go batch hunting. Open the Bulk API job, read the failed batchs own error, and you will usually find a malformed SOQL query, a CSV payload problem, or an unsupported operation in that batch alone. Fix that batch, resubmit only the failed portion, and the health fields land without a risky full reload.