Versioning and rollback
almyty keeps a record of every change to an agent, so you can always see who changed what and when, and put an earlier version back. The same goes for your tools, APIs and gateways. There is nothing to turn on.
See what changed
Open the agent and stay on its Overview tab.
- Change history lists each version: who changed it and when. Expand one to see exactly which settings changed.
- Audit log, below it, records everything that happened to the agent: created, changed, activated or paused, a version saved, a rollback, a run.
Go back to an earlier version
A workflow agent keeps a copy of its steps every time you save a change to them. The copies are numbered and listed under Pipeline versions on the Overview tab.
- Find the version you want under Pipeline versions.
- Click Rollback and confirm.
The agent’s steps are replaced with that version, and the rollback is recorded in the audit log. Newer versions are never deleted, so you can go forward again at any time. Test the agent after a rollback to make sure it behaves as expected.
An autonomous agent has no step copies to roll back to; its changes are in the Change history and the Audit log on the same tab.
For developers
Audit log events:
| Event | Description |
|---|---|
created | Agent was created |
updated | Configuration, pipeline, or tools were modified |
activated / deactivated | Status changed |
version_saved | A version snapshot was created |
rolled_back | Pipeline was restored from a previous version |
invoked | Agent was executed |
To take a named snapshot with a changelog of your own, call POST /agents/:id/versions with { "changelog": "..." }; the dashboard has no button for it. Doing this before restructuring a pipeline gives you a named restore point.