v3 · untested/ 10Changed
Since the last test the step “Slack message to sales” was added.
Then
The test of the current version finished.
Activation blocked · run a test for v3 first
Peak Automations · Versions
Every change becomes a new version.
Only what is tested goes live.
When you change an automation by sentence, Peak shows the difference and creates a new version. The previous one is kept. Only the current version can go live, and only after a passed test of exactly that version.
Change an automation safelyIllustrative example · sample data · nothing is changed
EXAMPLE / LIVE PREVIEWOne check.
One check.
The fitting step.
01 / Example value
Is the current version tested?
02 / What Peak Automations showsSince the last test the step “Slack message to sales” was added.
Activation blocked · run a test for v3 first
Change the example value. The next step follows the check.
Sample data · nothing runs
One example. Two paths.
The check
decides the next step.Compare both paths below ↓
decides the next step.Compare both paths below ↓
Two example versions
Is the current version tested?
Schematic example. In the product each version shows whether its test passed.
v3 · passed/ 10Checked
The test of the current version finished.
You can activate v3 · v2 is kept
Trust needs clarity
What versions do, and what they do not.
01 / The existing evidence
An example, not a history
The versions on this page are made up. Your version history sits on your automation.
- v3 · untested/10Since the last test the step “Slack message to sales” was added.Activation blocked · run a test for v3 first
- v3 · passed/10The test of the current version finished.You can activate v3 · v2 is kept
02 / Your check
No test on past data
Running a new version against past events is planned and not available today.
4 / 1010 / 10
Compare both paths and their reasons.
03 / The clear limit
No silent switch
A changed automation does not keep running untested in its new form. You activate it on purpose.
Example│Nothing runs
The next step
Change boldly, go back safely.
Start Peak Automations and see how a change becomes a tested version.
Change an automation safelyPeak Automations · VersionsWhat is new?
Illustrative example · sample data · nothing is changed
Frequently asked questions
Are old versions kept?
Yes. Every change creates a new version; earlier ones stay in the history.
Does a changed automation keep running right away?
No. The new version only goes live after a passed test, and you activate it on purpose.
Can I test a version on past data?
Not yet. Testing on past events is planned.