agent flagged the DRAFT watermark removal as a substantive change in the final version

Not specified by the original author.

TL;DR The final version dropped the DRAFT watermark and the agent flagged its removal as a substantive change. Watermarks, stamps, and banners are revision markings, not contract language, so strip them from both versions before diffing. The redline should cover the agreement, not the stationery.

What the bogus change looked like:

- DRAFT (watermark, every page) marked as removed content

Steps

1. Confirm the flagged change is only the watermark. Check whether the diff's watermark entries correspond to any actual clause text. Command: inspect the flagged regions and verify they contain only the watermark text with no clause language. Expected: every watermark flag is pure marking, no operative text involved.

2. Add a pre-diff cleanup pass that removes watermarks, stamps, and banner text from both versions: drop diagonal or background watermark text layers, and strip repeated header and footer strings. Expected: re-running the diff no longer mentions the watermark at all.

3. Keep a separate revision-markings report: record which markings each version carried, like DRAFT on v3 and none on v4, as metadata rather than diff content. Expected: the redline summary covers clause changes, with a one-line note that the DRAFT watermark was removed in the final.

4. Generalize the cleanup to other markings your pipeline will meet: CONFIDENTIAL banners, page stamps, and Bates numbers. Expected: future draft-to-final comparisons stay clean regardless of which markings change.

Use this when

• Draft-to-final comparisons flag watermark or stamp removal as changes
• Diffs include header, footer, or banner text that is not part of the agreement
• The counterparty's versions carry different revision markings
• Your redline change list is polluted with non-clause differences

Not for this skill when

• The marking is part of the executed agreement, like a notary stamp on the signature page, which deserves its own handling
• Watermark text overlaps clause text in a scanned PDF, clean the image rather than the text
• You need a forensically complete diff, keep the raw diff archived
• The only difference between versions genuinely is the watermark, then say so plainly

Variant phrasings

• agent flagged DRAFT watermark removal as a substantive change
• how to exclude watermarks from contract diffs
• redline showing watermark differences instead of real edits
• draft to final comparison polluted by revision markings
• strip headers footers and watermarks before diffing contracts

Why it happens

Watermarks and stamps live in the document as text or image layers, so a naive diff sees "DRAFT" present in one version and absent in the other and reports it like any other deletion. The diff has no concept of document furniture versus operative language, so revision markings get the same weight as a changed indemnity cap. Humans instantly discount the watermark; the agent needs to be taught to.

Edge cases

• A watermark that obscures clause text in a scan is a readability problem, flag the obscured region rather than silently stripping it.
• Bates numbers change on every page of every version, always exclude them or they will dominate the diff.
• Some stamps carry dates, like a received stamp, which can matter for timing disputes, log stamp metadata even while excluding it from the clause diff.
• Headers containing the agreement title may legitimately change if the title changed, compare header text as metadata before stripping.
• If the final version should NOT have lost its watermark, like a confidential draft that went out unmarked, that is a process failure worth escalating, not diff noise.

Provenance

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

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

Thread query: agent flagged the "DRAFT" watermark removal as a substantive change in the final version

TL;DR:

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 Collection reorder agent by acting on the exact symptom first: build the reorder list strictly from the collection membership export, reject any title that does not match an exported identifier, and show the final order as identifiers with titles so invention is visible before applying. 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 invented an article draft not present in source data

Use this when

• Work in Collection reorder agent shows this exact symptom: Agent invented an article draft not present in source data.
• 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 Collection reorder 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: build the reorder list strictly from the collection membership export, reject any title that does not match an exported identifier, and show the final order as identifiers with titles so invention is visible before applying. 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 Collection reorder 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 invented an article draft not present in source data

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 hallucinating article draft not in source data for reorder a help center collection error hallucination failure

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

Collection reorder 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

Planning an order from a topic description invites plausible article titles the collection does not contain, and applying that plan fails or worse, links wrong articles.

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: Collection reorder 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_19dN5gXJtgEK9QtmWrMztw

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

Thread query: agent hallucinating article draft not in source data for reorder a help center collection error hallucination failure

TL;DR: Fix this in Collection reorder agent by acting on the exact symptom first: build the reorder list strictly from the collection membership export, reject any title that does not match an exported identifier, and show the final order as identifiers with titles so invention is visible before applying. 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.