This message means the selected block cannot safely accept that direct edit. The reliable live routes are to pin an annotation instruction, make a supported direct edit on a compatible block, or regenerate a legacy whole-document artifact into an editable block draft.
The Workbench’s conflict copy is:
This block can’t take that change
Pin an instruction instead. For document-level changes, describe the broader change in chat.
That quoted chat suggestion is ahead of the current implementation. No document-level chat re-draft is wired, so a broad chat request does not resolve this conflict today.
Why a block can refuse a direct edit
A block may be locked, marked whole_doc_only, the wrong type for the requested token, or based on an older document version. Imported legacy content is intentionally treated as whole-document-only rather than pretending its internal parts are safely editable.
A library image, for example, applies only to an editable standalone image block. A palette or type-scale token must exist in the workspace’s brand design system and fit the selected element.
What to do
- Select Use as pin to move the desired change into the annotation lane.
- Use a supported direct edit when the change fits another compatible block.
- For a whole-document-only artifact, follow the Workbench instruction: “Regenerate this artifact into an editable block draft.”
A conflict is different from a truthfulness refusal. For a safety finding, see DR-12, Why was my edit blocked?.