Skip to content

Reference

Troubleshooting

The things that actually go wrong, and what each one is telling you.

Writes

HTFLOW_WEBFLOW_RULES_VIOLATED

The section broke a rule in the Webflow rulebook and was not saved. The response names what failed.

The fix is to regenerate the section so it satisfies the rules — not to retry the same source. The usual culprits are CSS shorthand, a media query at a width other than 991/767/479, a ::before or ::after, or JavaScript selecting by class. See the rulebook.

A write is refused as out of date

Something else changed the page, section or site since you read it. Read it again to get the current revision, reconcile your change against what is now there, and write once more.

An agent hitting this repeatedly is usually writing without reading first — see Agent workflow.

Export

Copy to Webflow reported success but nothing pasted

Browsers only allow a clipboard write while a click is still being handled. Press the button a second time; it copies the payload it already prepared rather than regenerating anything.

Also make sure the Webflow canvas has focus before you paste — Webflow reads the clipboard on the canvas, not in a panel.

It pasted as a code embed instead of elements

That happens when plain HTML reaches the clipboard instead of Webflow's own format. Copy again from HTFlow rather than copying markup out of a code view.

On the Webflow canvas

A section is invisible in the Designer

Almost always opacity: 0 set in CSS for a scroll animation. Webflow's canvas honours it, so the section renders empty.

Set the opacity at runtime instead and reveal it with an IntersectionObserver — the pattern is on JavaScript rules.

An element renders wrongly after interaction

Check for classList.add/remove/toggle. Webflow renders from the class list, so state carried on classes confuses the canvas. Use data-state, data-open or aria-expanded.

Styles are missing at a narrower width

A media query at a width Webflow has no viewport for is dropped on import. Only 991px, 767px and 479px survive — see Breakpoints.

AI and access

An MCP client connects but shows no tools

The connection reached the server but did not authenticate. Check the API token — see API tokens.

The agent panel will not run

It has no AI of its own. Add an OpenRouter key under Settings → AI Keys, or drive the site from an MCP client instead.