This article covers the most common things people run into after connecting Webflow to wxrks, organized by symptom. For how the connector works day to day — setup, content scanning, Components, and Field exclusions — see wxrks - Webflow Connector.
A delivered translation shows an error
When wxrks finishes translating a document, the connector downloads the translation and writes it into your Webflow site. If that final write fails for a specific document and language, the Runs page shows an Error status on that row — together with the exact reason Webflow reported, including which field was rejected.
An error here never means the translation was lost. It is safely stored in wxrks, and the connector automatically retries failed deliveries about once an hour. You can also fix the cause and click Redeliver on the errored row to push it again immediately.
The most common causes:
The item has no locale variant yet (CMS items). Webflow's API cannot create a new locale variant for an item that already existed before that language was enabled. The error says so explicitly ("This item has no '…' locale variant in Webflow yet"). Fix: open the item once in Webflow's CMS and add the language (Collection settings → Localization), then redeliver — from then on it syncs automatically.
The translated slug is already taken. With Slug handling set to "Translate" or "Transliterate", two items whose translated names collapse to the same words can produce the same slug — and Webflow requires slugs to be unique per language. The connector resolves this automatically: it delivers all the translated content, keeps the item's existing slug, and shows a note on the run explaining what happened. If you want a distinct translated slug anyway, adjust it manually in Webflow afterwards. Choosing "Keep the source slug" in Settings → Slug handling avoids slug collisions entirely.
A field's character limit was exceeded. Translations often run longer than the source text. If a plain-text field has a maximum length configured in Webflow, an overlong translation is rejected and the error names the field ("Field value exceeds maximum length…"). Shorten that segment in the wxrks editor and redeliver — or raise the field's limit in Webflow's collection settings.
Broken formatting in a rich-text field. If HTML markup was damaged during translation (for example a deleted closing tag), Webflow rejects the value. Repair the segment's tags in the wxrks editor and redeliver.
A technical value came back altered. Fields that hold non-language values (option lists, CSS class names, internal codes) can fail validation if translation changes them. Prevent this class of error entirely by excluding those fields in Settings → Field exclusions (or, for component text, Settings → Component property exclusions) — they will stop being sent to wxrks at all.
The fix workflow is always the same:
Open Runs, expand the run, and read the error on the failing row — it names the field and the reason.
Fix the cause — in the wxrks editor, in Webflow, or in the connector's Settings.
Click Redeliver on the row, or simply wait: the connector retries on its own every hour.
One reassurance worth repeating: a delivery error affects only that one document and language. Every other document in the run delivers normally, and nothing already translated is lost.
A static page or component shows no word count (or "0 words")
Symptom: in the content browser, pages and components show 0 words (or a dash) instead of a real number.
Cause: word counts are precomputed for CMS entries only. For static pages and components, computing a word count up front would require fully scanning every page of the site just to browse the list, so the connector deliberately skips it — the number you see next to a pages folder is a page count, not a word count.
Fix / clarification: a page or component showing no word count is not empty. The real, counted word total appears after you send it, on the Runs page (per work unit and per run).
A brand-new page doesn't show up in the connector
Symptom: you just created a page in Webflow and it isn't listed in the connector's content browser yet.
Cause: the connector caches the site's page list for up to ~30 minutes to keep browsing fast.
Fix: wait — a page created moments ago can take up to that long to appear — or reopen the Translate page to force a refresh sooner.
I sent a page but some of its text didn't arrive
Symptom: after sending a page, part of its visible text is missing from the wxrks project.
Cause: this is almost always about how that text was built in Webflow, not about the page selection. Text can live in several different "homes" — plain page elements, Components, CMS fields, HTML embeds, or images/SVGs — and only some of those belong to the page itself. See wxrks - Webflow Connector's "What does the connector scan?" section for the full breakdown of what's scanned and what isn't.
Fix / diagnostic tip: open the page in the Webflow Designer and click the "missing" element. The Designer shows you immediately whether it's a component instance (green outline / component panel) or a CMS-bound element — that tells you which section of the connector actually covers it, or whether it's out of scope (embed, image text) and needs a manual step.
My pages don't appear in Settings → Field exclusions
Symptom: static pages are missing from the Settings → Field exclusions screen.
Cause: Field exclusions applies only to CMS collection fields — it lets you mark specific fields of a collection (e.g. a SKU or a color code) as not-for-translation. Static pages don't have fields, so they are never listed there. That's by design, not a missing page.
Fix / where to go instead: use Settings → Component property exclusions — the equivalent control for page and component content, where you can exclude specific component properties (e.g. a width setting or a CSS class stored as text) from translation. See the Field exclusions section of wxrks - Webflow Connector for more on both controls.
Webflow doesn't match the translation I made on wxrks
Symptom: a translation that finished and was reviewed on wxrks doesn't match what's currently live in Webflow.
Cause: the same document was sent again in a later run — by a teammate, a test, or an automation — and Webflow keeps only one version of a locale's content, so the newest delivery always wins. Nothing is lost on the wxrks side: the original reviewed translation still exists in its original run, it's just not the version currently live in Webflow.
Fix: open the document's History on the Translate page to find the run with the correct translation, open that run on the Runs page, and click Redeliver on that document's row and language. See wxrks - Webflow Connector's "Multiple deliveries, overwrites, and history" section for the full mechanics of runs, deliveries, and history.