Understanding Flow Version History
Learn how FlowHunt AIStudio automatically manages your Flow version history, and how to review or restore previous versions if needed.
2 min read
Version History
AI
+2
When working in FlowHunt AIStudio, understanding the distinction between Run Flow and Publish Flow is essential for safe, controlled workflow development, especially if your Flow is already active in production (for example, embedded in a website chatbot). Below, we clarify the roles and recommended use cases for each function.
Run Flow – For Safe Testing
The Run Flow button allows you to test and experiment with your latest changes privately before exposing them to end users.
What Happens?
- You can interactively run your Flow with your most recent, unpublished edits.
- Only you (the editor) see the effects of these changes; your live users do not.
- Ideal for debugging or perfecting complex logic, text, or integrations.
Use Case Example
You want to refactor a step in your Flow or add a new integration. Use Run Flow to test changes and verify the output, all while your live users continue to interact with the unchanged, published version.
Publish Flow – Making Updates Live
The Publish Flow button makes your changes public by replacing the existing version used everywhere the Flow is deployed (e.g., on your website or chatbot).
Our AI Agent will automatically analyze the new changes and generate a commit message. You can add your message instead or edit the generated one. Once you’re done, hit Publish and a new version gets created. You can view and manage past version via version control .
What Happens?
- The current state of your Flow, including all recent modifications, becomes the new live version.
- All users and integrations connected to the Flow experience the updated functionality immediately.
Use Case Example
Once you’ve validated your changes with Run Flow, use Publish Flow to update the production system for all users.
Ready to grow your business?
Start your free trial today and see results within days.
Best Practice
Always test flow changes with Run Flow before using Publish Flow to push updates live. This ensures seamless and bug-free user experiences.
