Troubleshooting
The project page shows two stages — Sync moves Notion into Framer CMS, Publish pushes Framer CMS to your live site. Knowing which one failed tells you where to look, because they fail for completely different reasons.
The sync worked but the site has not changed
Section titled “The sync worked but the site has not changed”This is the most common one, and usually nothing is broken.
Sync and publish are separate. A finished sync means your content is in the Framer CMS. Your live site only changes when a publish runs — either auto-publish, or you pressing Publish in Framer.
Check the Publish stage. If it says Off, auto-publish is not on for this project: turn it on, or publish from Framer when you are ready.
Publish failed
Section titled “Publish failed”Your content is safely in Framer CMS. Only the push to the live site failed, so nothing is lost — the site is showing its previous version.
”Framer stopped while publishing / optimising the site”
Section titled “”Framer stopped while publishing / optimising the site””Framer accepted the publish and then could not build the site. The message names the first problems Framer reported.
Fix those in Framer — they are about the site, not the sync. KnotCMS does not keep retrying, because identical content produces an identical result. Your next sync tries again.
”Publishing is currently unavailable”
Section titled “”Publishing is currently unavailable””Framer is refusing the request. Usually the site has been published too often in a short window, and it clears on its own.
If it persists, open the project in Framer and press Publish by hand:
- Framer refuses too — the problem is the site or the Framer account, and nothing in KnotCMS gets past it.
- It publishes fine — contact support with your project URL.
Notion edits are not syncing on their own
Section titled “Notion edits are not syncing on their own”Auto-sync needs nothing set up in Notion — it is only the toggle. So the answer is on the project page, in the Auto-sync field.
Give it two minutes first. KnotCMS checks for changes once a minute, so an edit you made seconds ago has not been looked at yet.
| Auto-sync shows | What to do |
|---|---|
| Polling, every minute | Working normally. If an edit still has not landed, see the two cases below. |
| Off | Turn auto-sync on under the project’s Settings tab. |
| Paused, free syncs used | See Automatic syncing has paused. |
| Paused, needs attention | See Automatic syncing has paused. |
Two edits that a once-a-minute check cannot see:
- You deleted a row and changed nothing else. The item stays in Framer until your next edit. Click Sync now to remove it straight away — this is expected, not a bug.
- You edited text inside a page body. KnotCMS watches database rows. Change a property instead, or click Sync now.
Sync now always works regardless, so if manual syncs are fine and automatic ones are not, the Auto-sync field is where to look.
Automatic syncing has paused
Section titled “Automatic syncing has paused”Nothing is deleted in either case, and neither needs you to reconnect or reconfigure the project.
”Paused, free syncs used”
Section titled “”Paused, free syncs used””The headline reads Free syncs used up. The free plan includes 10 syncs for the life of the project and they are now gone.
The allowance covers automatic and manual runs alike, so this is the end of both until you upgrade. Everything stays visible and your Framer content stays where it is. Subscribe and automatic syncing resumes within a minute — there is nothing to reset.
”Paused, needs attention”
Section titled “”Paused, needs attention””The headline reads Auto-sync paused: KnotCMS could not read your Notion database several times in a row, so it stopped retrying. The reason is shown underneath. The usual causes are:
- The KnotCMS integration was removed from the database in Notion — re-grant it access.
- The database was deleted or moved out of reach — restore it, or reconfigure the project onto a different one.
To clear it: fix the cause, then click Sync now. One successful manual sync resumes automatic syncing.
A field is not coming through
Section titled “A field is not coming through”- The column is the wrong type in Framer. A column that already exists keeps its type — mapping it differently in KnotCMS will not convert it. See Changing a column’s type.
- The property type is not mapped. Relations, rollups, formulas, people and multi-select are not synced. Supported field types lists what is.
- The row is empty in Notion. A blank row syncs as a blank item, with a slug made from its page id. Delete it in Notion, then click Sync now — a deletion on its own is not always picked up by the automatic check.
Images are missing
Section titled “Images are missing”Framer fetches image URLs itself, and some hosts refuse. When that happens the sync finishes without those images rather than failing, and the project page shows FRAMER_ASSET.
Notion’s own file URLs also expire. For images that need to last, host them somewhere stable and map the URL.
An error code on the project page
Section titled “An error code on the project page”Every code, what it means and how to clear it: Error codes.
Still stuck
Section titled “Still stuck”Contact support with the email you sign in with and your project URL. If a sync or publish failed, the message shown on the project page is the useful part to include.