Workflow Version History
Every AI Employee's workflow accumulates changes over time as builders add agents, adjust bindings, modify prompts, and tune conditional logic. Workflow Version History provides a structured record of these changes, enabling teams to understand what changed, when, and by whom.
What Version History Tracks
Each time a workflow is saved or published, the platform records a version entry (also called a change log entry). A version entry captures:
- Timestamp: When the change was made.
- User: Who made the change.
- Change type: The nature of the modification (e.g., workflow publish, configuration update, agent addition or removal).
- Workflow snapshot: The complete workflow definition at that point in time, enabling comparison between any two versions.
Viewing Version History
To access version history for an AI Employee:
- Navigate to the AI Employee's configuration page.
- Open the Version History panel (accessible from the Workflow Builder or the AI Employee settings).
- Browse the chronological list of versions. Each entry shows the timestamp, author, and a summary of changes.
Viewing Existing Versions
The Version History view helps builders inspect previously saved workflow versions and understand how the workflow evolved over time. This is useful for:
- Debugging regressions: Identify which change caused a workflow to behave differently.
- Reviewing prior versions: Understand what changed between existing workflow versions.
- Audit compliance: Demonstrate what configuration was active at a specific point in time.
Reverting to a Previous Version
If a workflow change introduces unexpected behavior, you can revert to a previously published version:
- Open the Version History panel.
- Select the target version to update the workflow canvas and show that version's workflow definition.
- Click Restore to immediately publish that version by creating a new version entry with the restored workflow contents.
Restoring a previous version does not delete any history. It immediately republishes the selected version as a new version entry, preserving the full audit trail.
Version History and Audit Logs
Workflow version history is complemented by the platform's Audit Log, which records broader events beyond workflow changes:
| Record Type | Scope | Examples |
|---|---|---|
| Version History | Workflow definition changes | Agent added, binding modified, prompt updated, workflow published |
| Audit Log | AI Employee-level events outside workflow versioning | AI Employee configuration updates, data source additions, and similar AI Employee-level configuration changes |
Together, version history and audit logs provide a fuller picture of an AI Employee's evolution -- combining workflow version changes with other AI Employee-level activity.
Best Practices
- Publish incrementally: Make small, focused changes and publish after each one. This keeps the version history granular and makes it easier to identify which change caused a specific behavior.
- Use version history for traceability: Review prior published versions to understand how the workflow changed over time and to restore a known-good version when needed.
- Use audit logs for compliance: For regulated environments, combine workflow version history with audit logs to create a complete change audit trail.
Previous: Workflow Validation | Back to: Core Concepts Index