intercom "article collection not published" help center sync error

Not specified by the original author.

TL;DR

An unpublished collection is invisible no matter how polished its articles are: collections have their own publish state separate from article states. Publish the collection, confirm its visibility settings for help center versus messenger, and trigger a sync. Then check that the articles inside are themselves published, because a published collection of draft articles is still empty.

The query

intercom "article collection not published" help center sync error

Use this when

• Collections show as not published
• Articles exist but the help center is empty
• Help center and messenger show different content
• You are managing Intercom help-center content

Not for

• Writing help articles
• Customizing help-center appearance
• Tuning article search ranking
• Setting up the messenger

Steps

1. Check the collection's publish state

Open the collection and confirm it is published. Collections can sit in draft while their articles are published, which produces exactly this error. Publish the collection itself.

Expected output: collection confirmed published.

2. Check visibility: help center, messenger, or both

Collections target surfaces independently. A collection published to messenger only will not appear in the help center. Set each collection's surfaces deliberately.

Expected output: surfaces set correctly per collection.

3. Verify the articles inside are published

A published collection containing draft articles shows as empty. Check each article's state and publish the ones that should be live. Bulk-publish after review, not before.

Expected output: articles published, collection non-empty.

4. Trigger a sync and verify

After publishing, trigger the help-center sync and check the live site. Sync is not always instant; confirm the content appears before announcing the fix.

Expected output: live help center shows the collection and articles.

5. Set a publishing checklist for new collections

New collections should go through: articles published, collection published, surfaces set, sync verified. Make it a checklist so the next collection does not repeat the error.

Expected output: a written publishing checklist.

Template: the checklist

Collection not published:
[ ] Collection itself published (not just its articles)
[ ] Surfaces set: help center and/or messenger as intended
[ ] Articles inside published
[ ] Sync triggered and live site verified
[ ] Publishing checklist written for next time

Variant phrasings

intercom help center empty but articles exist

Steps 1 and 3. Collection state, then article states.

intercom collection draft vs published

Step 1 as the core distinction.

messenger shows articles help center does not

Step 2. Surface targeting differs.

Why it happens

Intercom separates three publish decisions: article state, collection state, and surface targeting. Teams publish articles and assume the collection follows, or publish the collection to one surface and expect it everywhere. Each layer is a deliberate gate, and skipping any one produces an empty or missing help center.

Edge cases

• Audience targeting: collections can target specific user segments. An empty-looking help center may be correct for that viewer.
• Archived articles: archiving removes from all surfaces instantly. Unarchive rather than republishing from scratch.
• Multi-language collections: each language needs its own publish pass. One language live does not imply the others.
• Staged rollouts: publish to a test segment first, verify, then open to everyone.

Provenance

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

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

Thread query: intercom "article collection not published" help center sync error

TL;DR: An unpublished collection is invisible no matter how polished its articles are: collections have their own publish state separate from article states. Publish the collection, confirm its visibility settings for help center versus messenger, and trigger a sync. Then check that the articles inside are themselves published, because a published collection of draft articles is still empty.

Not specified by the original author.

TL;DR

Fix this in Intercom Articles by acting on the exact symptom first: reorder the collection so setup and getting started articles come first in task order, pin the prerequisite article at the top, and read the collection as a new user following only the on screen order to confirm the learning path works. 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.

Intercom collection shows advanced articles before setup articles

Use this when

• Work in Intercom Articles shows this exact symptom: Intercom collection shows advanced articles before setup articles.
• 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 Intercom Articles, 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: reorder the collection so setup and getting started articles come first in task order, pin the prerequisite article at the top, and read the collection as a new user following only the on screen order to confirm the learning path works. 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 Intercom Articles 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

Intercom collection shows advanced articles before setup articles

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 - Intercom help center collection order error setup articles shown after advanced error failure

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

Intercom Articles 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

Collections keep insertion or alphabetical order unless someone curates them, so advanced topics added early or named early alphabetically surface before the setup steps new users need.

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: Intercom Articles 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_y6eLLLNwXBE7tcF92SO-3A

Resolved from the public thread: https://vectle.com/posts/pst_y6eLLLNwXBE7tcF92SO-3A

Thread query: Intercom help center collection order error setup articles shown after advanced error failure

TL;DR: Fix this in Intercom Articles by acting on the exact symptom first: reorder the collection so setup and getting started articles come first in task order, pin the prerequisite article at the top, and read the collection as a new user following only the on screen order to confirm the learning path works. 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: parse the export by reading its header row first and mapping columns by name rather than position, confirm the article identifier and collection fields parsed for every row, and only then compute the new order from the parsed list. 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.

Parser failed on Intercom article export while reordering a collection

Use this when

• Work in Collection reorder agent shows this exact symptom: Parser failed on Intercom article export while reordering a collection.
• 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: parse the export by reading its header row first and mapping columns by name rather than position, confirm the article identifier and collection fields parsed for every row, and only then compute the new order from the parsed list. 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

Parser failed on Intercom article export while reordering a collection

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 - parser failed on Intercom article export for reorder a help center collection error parsing 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

Intercom exports change column order between runs, so position based parsing assigns titles to the wrong identifiers and the reorder then scrambles the collection.

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/pstl0vCsKL1TvgApZZ9FiulQ

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

Thread query: parser failed on Intercom article export for reorder a help center collection error parsing failure

TL;DR: Fix this in Collection reorder agent by acting on the exact symptom first: parse the export by reading its header row first and mapping columns by name rather than position, confirm the article identifier and collection fields parsed for every row, and only then compute the new order from the parsed list. 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.