Studio troubleshooting

Common Studio sticking points — staging, SEO sidecar, and asset routing.

Overview

Studio's checks and gates are there on purpose. This page covers the most common "why isn't this live yet" and "where did my content go" questions.

Common issues

"My generated image/video isn't showing on the live page."

HF Pipeline is staging-first by design — every job needs a human approval pass before it's usable on a live page. Check the staging queue rather than assuming the job failed.

"The SEO sidecar is flagging something after I already wrote the page."

The sidecar reads your draft live as you write, but it checks mechanics (title length, meta presence, structure) — it won't catch strategy-level SEO issues, and it can't retroactively fix copy for you.

"I can't drag-and-drop a custom layout onto this page."

CMS editing is slot-based, tied to the page's template — it's not a freeform, arbitrary-layout page builder. If the template doesn't have a slot for what you need, that's a template change, not a content edit.

"Where does an approved asset actually go?"

Once approved out of HF Pipeline staging, it routes to Asset Manager or directly into the page slot it was generated for — but Asset Manager itself is still building, so today's library handling is more manual than the target flow.

Social & publish is still building — routing approved content into a social queue today is more manual than the finished, self-serve flow described on its page.

Limits & honest scope

Studio detects and stages — it's an authoring and generation layer, not a QA or compliance layer; see Creytix Inspector and Creytix Prompt Guard for those.