Webflow CMS Publishing & Single-Item Publishing Debugging

We are experiencing CMS publishing issues in Webflow that are blocking our ability to use single-item publishing.

The key issues:

• Certain CMS items show "Changes in draft" even after a full publish.

• Attempting to publish those items triggers the error: "Field 'service': Expected value to be a single line" — but the service field no longer exists in our collection.

• Adding a placeholder field and doing a full publish did not clear the error.

• This is preventing other CMS items from being published individually (single-item publishing fails).

Goal: Resolve schema/data mismatch so that all CMS items can be published normally, and single-item publishing works again without losing existing URLs or live content.

What we need from you:

• Identify the root cause of the service field validation error.

• Repair or clean affected CMS items while preserving slugs, content, and live URLs.

• Ensure CMS and live site are fully in sync, enabling single-item publishing going forward.

• Provide a short write-up of the fix for our records.

Requirements:

• Proven Webflow debugging experience, specifically with CMS schema and publishing issues.

• Ability to troubleshoot deleted/renamed field conflicts in Webflow collections.

-Clear communication and fast turnaround.

Deliverable:

A fully functioning Webflow site where all CMS items can be published individually without errors, and no “Changes in draft” status remains unless truly unpublished content exists.

• Identify the root cause of the service field validation error
• Repair or clean affected CMS items while preserving slugs, content, and live URLs
• Ensure CMS and live site are fully in sync, enabling single-item publishing going forward
• Proven Webflow debugging experience, specifically with CMS schema and publishing issues
• Ability to troubleshoot deleted/renamed field conflicts in Webflow collections
• Clear communication and fast turnaround

• Certain CMS items show "Changes in draft" even after a full publish
• Attempting to publish those items triggers the error: "Field 'service': Expected value to be a single line" — but the service field no longer exists in our collection
• Adding a placeholder field and doing a full publish did not clear the error
• This is preventing other CMS items from being published individually (single-item publishing fails)
• Goal: Resolve schema/data mismatch so that all CMS items can be published normally, and single-item publishing works again without losing existing URLs or live content
• Provide a short write-up of the fix for our records