Publishing and recovery
Fix preflight errors and warnings
Use preflight results to find blocking data issues, understand warnings, and see why Publish now is disabled.
What this article helps with
Use this guide when QuillDock finishes preflight but still shows warnings, errors, or a disabled Publish now button.
This guide is for
Anyone preparing to publish changes from a saved source into Wix CMS.
What you'll see
- Counts for create, update, unchanged, and stale rows
- Warning and error totals
- Row-level details that point to the issue
Publish nowenabled only when the latest preflight is fresh, passing, and still matches the current configuration
What warnings and errors mean
- Warnings mean something needs review but may not stop a later publish
- Errors block publish until the underlying issue is fixed
- Preflight never writes to Wix CMS. It compares the current source and target and saves the result for review
Common reasons preflight is blocked
- Blank match-key values in the source
- Duplicate match-key values in the source or target
- Invalid numbers, booleans, dates, or URLs
- A source with zero usable rows
- The source is over the current record limit
- The preflight result is too old to publish from
- Source, target, or mapping changed after the preflight finished
What to do
- Open
Preflight review. - Read the summary and row details.
- Fix the mapping or source data that caused the blocked rows.
- Run preflight again to create a fresh result.
- Publish only from the latest passing preflight.
Why Publish now may still be unavailable
Publish now stays unavailable when:
- The preflight is not passing
- The preflight is no longer fresh
- The configuration changed after the preflight was created
- Billing or trial status does not currently allow publish
When to contact support
Contact support if QuillDock shows a blocking condition you cannot resolve from the preflight details, or if publish stays disabled even after you run a fresh passing preflight.
Related guides
Preflight reviewFix mapping issuesRestore from a backup
Still stuck?
Contact support from this article.
If the steps above did not resolve the issue, send us a note and we will pick up from the workflow you were reviewing here. You can also email support@quilldock.app.