7.7 · Fix a paused collection
When someone changes a collection's fields in your CMS, GrowthOS pauses publishing into it. Re-run the field mapping and it publishes again in about 2 minutes.
If publishing into one collection suddenly fails while the rest of your CMS connection keeps working, someone changed that collection's fields in your CMS. Re-run the field mapping from CMS Connections and the collection publishes again, usually in about 2 minutes.
A field change means added, renamed, removed or re-typed fields, or a field that became required. Reordering fields doesn't count. GrowthOS mapped its article fields to the old structure, so it pauses that collection rather than guess where each part of the article belongs now. Nothing is lost, and other collections keep publishing.
How to recognize it
- The publish card refuses the article for that collection, where publishing into it worked before.
- The collection's setup screen shows a banner reading Webflow's fields changed (or your CMS's name in place of Webflow), which says publishing into it is paused.
- Other collections still publish. The pause is per collection: a blog collection can be paused while a resources collection on the same connection publishes normally.
The same pause applies on every supported CMS: a Webflow collection, a WordPress post type, a Sanity document type, a Strapi collection type, or a Storyblok or Contentful content type. On Sanity, the trigger is the deployed Studio schema, so redeploy the Studio after a schema change before you remap.
How to fix it
Open the collection
Go to Workspace Admin → CMS Connections, open the connection, and click the paused collection. If the collection shows Finish setting up, click that instead; it opens the same screen.
The fields changed banner sits at the top, with 3 numbered steps below it.
Let an agent propose the mapping
Under Let an agent propose the mapping, click Propose mapping. An agent, a GrowthOS worker that drafts for you to approve, reads the collection's current fields and suggests an article field for each one.
When it finishes, each row it can place is filled in with a suggestion, a confidence and a reason; the rest are left for you to pick in the next step. Nothing is saved yet.
Review and confirm the mapping
Under Confirm the mapping, check every row. Rows the agent filled in carry an Inferred tag. Rows it couldn't place show Choose an article field… and need you to pick one.
Check these first:
- Required fields, marked with a red asterisk. Each one needs an article field or a fixed value. A newly required field, like a category the site recently made mandatory, is a common cause of the pause. If every article gets the same entry, pick it as a fixed value.
- The body field. Exactly 1 field receives the article body. The wrong field here publishes an empty article.
- Anything you're unsure of. Ask whoever changed the CMS, or your GrowthX team, before confirming.
Click Confirm mapping. The button stays disabled until every required field is covered and the body has a home, so you can't confirm a mapping that would fail.
Test with a sample
Under Test with a sample, run the test. GrowthOS sends a throwaway article into the collection as a draft and reads it back, field by field. Nothing goes live, and the test article is deleted afterwards.
You see what your CMS received for each field. Check that the body kept its headings, lists and links, and that each field landed where you expected.
Finish and republish
Click finish. The banner clears and the collection is ready. Open the article that was refused and publish it again from its publish card.
Stop it from catching you on a deadline
There is no setting to skip the pause. (Verified 2026-10-22.) Publishing into a structure GrowthOS no longer recognizes could put content in the wrong fields or drop it entirely, so the pause holds until someone confirms a mapping.
- Remap right after a CMS change. Run the steps above as soon as anyone edits a connected collection's fields, before the next article is due.
- Ask your web team for a heads-up before they rename, add a required field to, or change the type of a field in a connected collection.
- Any Owner or Operator can remap. You don't need GrowthX for this; see Roles and permissions.