Automation Versions (Audit History)
Every automation keeps an immutable version history of its configuration. Versions exist so you can always answer: "exactly what configuration was this run executed with, and who changed what, when?"
How versions are created
- Creating an automation records version 1.
- Every subsequent save of the automation records a new version (+1). There is no way to edit or delete a past version — the history is append-only.
What a version captures
Each version is a complete snapshot of the automation's operative configuration:
| Snapshot field | Notes |
|---|---|
| System prompt | The full composed instruction text |
| Model | The AI model the automation uses |
| Tool configuration | The exact tool allow-list |
| Trigger type and trigger configuration | On-demand / scheduled / webhook, plus cron, payload mode, etc. |
| Max runtime (seconds) | The runtime guardrail at the time |
| Max credits per run | The spend guardrail at the time |
| Dry-run flag | Whether the automation was in read-only mode |
| Created at / created by | Timestamp and the user who made the change — StackJack staff edits made on your behalf are attributed to the acting staff member |
Versions and runs
- Every run records the version it executed. Run history is therefore fully attributable at the data level: for any past run, the precise prompt, tools, and caps that were in force are recorded and retained.
- New runs always use the latest version. There is no way to pin an automation to an older version.
Viewing versions
The portal surfaces the version history on each automation's Version history page (/automations/{id}/versions) — a newest-first table of every version with its trigger, model, and dry-run/live mode. See Automation Version History and Rollback for the walkthrough. The portal does not yet label individual runs with the specific version they executed; if you need that mapping for a particular past run, the snapshot data is retained server-side and StackJack support can retrieve it.
Restoring an older version
You can restore any earlier snapshot as the live configuration from the Version history page — see Automation version rollback. Restore re-applies the snapshot's captured fields and records the rollback as a new version, so the audit trail is never lost and the change is reversible.