Version Control

How It Works

When you edit a published survey, changes are saved as a draft. Active respondents continue to see the published version until you click "Deploy Changes". This allows you to make updates without disrupting ongoing data collection.

If a user is actively completing a survey when you deploy a new version, they will continue with the version they started. Their in-progress responses are not affected by the deployment. New survey sessions will use the updated version.

Creating Snapshots

Save a snapshot before making significant changes. This creates a restore point you can return to if needed.

In the survey editor, click "Save Snapshot" and add an optional note describing the version. The current state is saved with a timestamp. You can then continue editing or deploy your changes.

Rolling Back

If you need to undo changes, you can roll back to any previous snapshot. Open the survey, click "Version History", browse snapshots with timestamps and notes, then select one to preview and restore.

Rolling back restores the survey structure but does not affect already-submitted responses. Existing response data remains intact.

Recommended Workflow

Save a snapshot before editing, make your changes in draft mode, test thoroughly, then deploy to make live. Monitor new responses and roll back if issues arise. Always save snapshots before major structural changes like adding/removing questions or modifying calculations.