3aa7199503
- Add Activepieces fork with SmoothSchedule custom piece - Create integrations app with Activepieces service layer - Add embed token endpoint for iframe integration - Create Automations page with embedded workflow builder - Add sidebar visibility fix for embed mode - Add list inactive customers endpoint to Public API - Include SmoothSchedule triggers: event created/updated/cancelled - Include SmoothSchedule actions: create/update/cancel events, list resources/services/customers 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
19 lines
840 B
Plaintext
19 lines
840 B
Plaintext
---
|
||
title: "Version History"
|
||
icon: 'clock'
|
||
description: "Learn how flow versioning works in Activepieces"
|
||
---
|
||
|
||
Activepieces keeps track of all published flows and their versions. Here’s how it works:
|
||
|
||
1. You can edit a flow as many times as you want in **draft** mode.
|
||
2. Once you're done with your changes, you can publish it.
|
||
3. The published flow will be **immutable** and cannot be edited.
|
||
4. If you try to edit a published flow, Activepieces will create a new **draft** if there is none and copy the **published** version to the new version.
|
||
|
||
This means you can always go back to a previous version and edit the flow in draft mode without affecting the published version.
|
||
|
||
|
||
|
||
As you can see in the following screenshot, the yellow dot refers to DRAFT and the green dot refers to PUBLISHED.
|