Troubleshooting Canvas

Common issues writers run into when using Canvas, with suggested fixes.

Common issues writers run into when using Canvas, with suggested fixes.

Make sure your Studio has been configured properly to allow Canvas to connect. This involves configuring and deploying the relevant Studio.

Check that the relevant fields aren't configured to be excluded from Canvas in your Studio schema. This requires a Studio configuration update and redeployment. See Configure Canvas for your content.

A few things to try:

• Simplify your document. Remove placeholder copy, draft notes, or inline instructions before running AI labeling.
• Use clear content breaks. Separate content for different fields into distinct paragraphs or sections.
• Add field name hints. Include a plain-text heading like "Title" or "Excerpt" above the relevant content.
• If results are still off, switch to manual labeling with the =l command for the problematic fields.

Field labels follow your schema's field order. When labels are applied, content reorders to match the structure defined in your content type. This is expected behavior: it ensures your document mirrors the Studio field order. The exceptions are modular content blocks and array items, where you control the order.

The @ reference shortcut requires at least read access to the connected Studio, and referenced documents need to be in the same dataset as that Studio. If you have Canvas-only access, you can work with field labels but won't be able to insert content references. Ask your administrator for Studio read access if your workflow requires references.

When you add a reference inside a field label, results are filtered to only include the document types specified in the content schema.