Skip to main content
Publishing turns an editorial draft into a version the runtime can execute.
Fictional corpus checks before publication

Fictional French-language demo domain; no customer data.

Before publishing

Studio distinguishes between:
  • blocking errors, which must be fixed before publishing;
  • warnings, which deserve review but may not prevent publishing;
  • the diff, which summarizes changes from the active version.

Three stages

1

Validation

The server checks identifiers, references, question types, dimensions, and information to collect.
2

Compilation

An asynchronous job prepares the decision artifact. You can leave Studio; the job continues on the server.
3

Activation

If compilation succeeds, the new version becomes active for sessions created afterwards.
A failed compilation never replaces the active version. Fix the reported cause or publish again; visitors continue using the latest valid version.
An existing session keeps the version it was created with. Publishing therefore does not alter an ongoing conversation.