Versioning

Publishing a new version

Each edit to a template is saved as a new numbered template version. Publish a version to make it available for new instances to be created from, and for existing instances to upgrade to.

Upgrading an instance

When a newer published version exists, an instance’s status shows update_available. Upgrading:

1. Re-materializes the instance’s flows as new flow versions on the same flow rows (so flow IDs — and anything referencing them, like phone-number assignments — are preserved).
2. Re-substitutes the instance’s previously-supplied field values.
3. Prompts only for fields that are new in the target version — a diff between the instance’s current template version and the target computes exactly which fields need new input.

Manual edits and upgrades

An upgrade re-runs field substitution against the target template version’s structure to produce the new flow version — it does not attempt to merge in changes a tenant has since made directly inside their materialized flow. If a tenant’s instance has diverged significantly from the template, review what an upgrade would change before applying it; the previous flow version remains in the flow’s version history if you need to compare or revert.