Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Version history gives you a timeline of saved journey states. This is one of the most valuable controls for smaller teams because customer-journey work often changes in bursts:
  • A workshop restructures the map
  • A cleanup pass removes stale work
  • A release changes the underlying flow
  • AI or collaborative editing moves faster than expected
Version history lets you inspect those changes without rebuilding the journey manually.

​
What version history captures

Custory records snapshots from events such as:
  • Session start
  • Session end
  • Auto-save
  • Milestone saves
  • Manual saves
These snapshots create a recoverable timeline instead of one fragile current state.

​
Open version history

From the journey editor, open the menu and choose Version history. Custory opens a history panel where snapshots are grouped by date and shown with metadata such as:
  • Trigger type
  • Time created
  • Label, if one exists

​
Understand snapshot types

Different snapshot triggers mean different things in practice.

​
Session started

Useful when you want to see the state at the beginning of a working session.

​
Session ended

Useful when you want to compare what changed during a focused work block.

​
Auto-saved

Useful for general recovery and for tracing ongoing edits.

​
Milestone

Useful when the journey reached a meaningful decision point or checkpoint.

​
Manual save

Useful when someone intentionally preserved a state worth returning to.

​
Review before restoring

The safest workflow is:
  1. Open version history
  2. Select the snapshot you care about
  3. Preview that version
  4. Confirm it is the state you want
  5. Restore only if needed
Do not restore based on timestamp alone. Preview first whenever the change matters.

​
Preview a snapshot

Preview mode lets you inspect an earlier state of the journey without immediately overwriting the current one. Use preview when:
  • You want to confirm whether a version contains the missing structure
  • You are comparing before-and-after states
  • You want to recover only after inspection
This is especially helpful after large workshop edits or cleanup passes.

​
Label important versions

Snapshots can be labeled so the team can recognize meaningful states quickly. Use labels for moments such as:
  • Before onboarding rewrite
  • Post workshop baseline
  • After Q2 cleanup
  • Before restoring shipped flow
Labels matter because timestamps alone are easy to forget, especially in fast-moving startup workflows.

​
Restore a snapshot

Restore when the safest move is to return the journey to an earlier state instead of manually reconstructing it. Restore is useful when:
  • A large edit went in the wrong direction
  • The structure was simplified too aggressively
  • Important context was removed
  • A workshop created more churn than clarity
Restore should be a deliberate team action, not a reflex.

​
When version history is most useful

Version history is especially valuable for:
  • Weekly journey maintenance
  • Cross-functional workshops
  • AI-assisted restructuring
  • Recovery after aggressive cleanup
  • Reconstructing decision context over time
Use version history as a confidence tool, not only as a rescue tool. A practical habit:
  1. Do bigger structural work in focused sessions
  2. Label major checkpoints
  3. Preview old states before restoring
  4. Restore only when rework would be slower or riskier
This helps the team move faster without fearing that every major edit is irreversible.

​
Common mistakes

​
Never labeling meaningful states

Important versions become hard to find later.

​
Restoring without previewing

You increase the chance of bringing back the wrong state.

​
Using history only after something breaks

History is also useful for understanding how the map evolved.

​
Treating every snapshot as equally important

Label and use milestone logic for the states the team may actually need again.