Version control
Last updated
Last updated
Every workflow keeps track of its version history, allowing you to manage changes, maintain different versions, and ensure stability. You can view your workflow's version history in the sidebar of the workflow canvas, where you'll see all versions along with who created them and when they were published.
A version represents a specific state of your workflow. When publishing changes, you can create either a major version (like 2.0, 3.0) for significant changes, or a minor version (like 1.1, 1.2) for smaller updates and fixes. This helps you and your team understand the scope of changes in each version.
The version history panel shows you all published versions of your workflow. For each version, you can see who created it, when it was published, and its current status - whether it's deployed and if it's set as the default version.
The default version of your workflow is what users get when they don't specify a particular version. It's typically your latest stable version, using the main URL without any version number. Setting a version as default is straightforward - simply open the version menu (three dots) and select "Set as default". This is particularly useful when you want to smoothly transition users to a newer version of your workflow.
Sometimes you'll want to see how an older version of your workflow behaved, or verify changes between versions. The preview feature lets you do exactly this. When you preview a version, you can test it fully without affecting your live deployment. This is invaluable when you're considering reverting to a previous version or just need to check how something worked before.
If you discover that a previous version worked better for your needs, you can revert to it at any time. Reverting makes that version active again, while maintaining all its original URLs and settings. It's important to note that reverting doesn't change which version is set as default - this remains a separate choice that you can make afterward.
Your workflow's URL structure makes it easy to access specific versions.
Default version: When a workflow is set as the default, it uses the main URL (e.g., https://your-company-id.lleverage.run/your-api-endpoint).
Non-default versions: If a workflow version is not the default, its URL will include the version number (e.g., https://your-company-id.lleverage.run/your-api-endpoint/2.1). This ensures that previous versions can still be accessed while the default version remains active.
You can have multiple versions of your workflow deployed at once, giving you flexibility in how you roll out changes. For any deployed version, you have several management options through the version menu:
Preview the version to test its behavior
Copy the CURL command for API testing
Set it as the default version
Deactivate it to prevent further use
Revert to make it active again
Whenever you're making changes to your workflow, you're working in a draft that won't affect any deployed versions. Think of a draft as your workspace where you can experiment freely. Only when you're ready to make your changes available do you publish them as a new version. This means you can take your time testing and refining your changes before they go live.
Remember that you can start a new draft from any existing version of your workflow. This gives you the flexibility to build on your latest changes or branch off from an older version if needed.