Templates keep their last 50 saved states
Every save on a template keeps the one before it, up to fifty, and any of them can be restored in a click.
Restoring appends rather than rewinds
When you restore an old version, the state being replaced is written to the history as a new entry rather than discarded. Putting an old version back therefore loses nothing, and an undo can itself be undone.
The alternative, rewinding to a point and dropping everything after it, is the behaviour people expect from a text editor and the wrong one for a template somebody else might be editing. A restore that quietly deletes a colleague's afternoon is the kind of feature you only get to ship once.
Where this is available
Version history is in the dashboard and the GraphQL API. The public REST API exposes no version routes, so it is deliberately absent from the reference: an endpoint that is not there should not be documented as though it is.
Related: Templates, Update a template over REST
Private beta
See the next one land
Beta members get the release note in the same batch email that opens their account.