Publish and versions
Why publishing freezes a version and what changes when republishing.
2 minutes read
On this page
Make a reviewed edit available through the public link.
Purpose
Keep drafts separate from the questions each participant actually answered.
When to use it
For the first collection and whenever blocks, logic or screens change.
Before you start
- A study with valid blocks
- Editor permission
Example
Publish v2 after revising the task while preserving v1 responses.
Step by step
- Review the draft. In the builder, use Test full flow after editing. Fix incomplete blocks, logic destinations and tasks with no exit. Questions · Logic · Screens.
- Publish. Open Share and use Publish. Read any blocking issue and return to the indicated block to fix it. Content is frozen in this version.
- Verify the link. Use preview to check appearance. To validate real integrations, open Test after publishing and follow the participant link. Testing the published version may generate a real response and consume quota.
- Identify the edition. In Results, use the version filter. Compare versions when the blocks and samples support a meaningful comparison. v1 and v2 retain their own responses.
Validate before collecting responses
The side preview lets you inspect a block; for Figma it is static. To validate draft rules and order, use Test full flow, without creating sessions or taking quota slots. Figma, recording, voice and AI follow-up require the published link. Test published opens the real /r/[token] link: it can create responses and consume quota. Separate these tests when analyzing your collection.
How to read the result
- New sessions use the published version
- Version filters let you analyze each edition
Cautions and limitations
- Editing the draft does not alter a published version.
- Sessions started before republishing stay on the earlier version.
Continue with the interactive guide
Related guides
Is something missing? Write to contato@uxtap.app.