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 — 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.