Fleet configurations and Update Manager
For Owners and Operators updating Studio deployments: a Fleet Configuration Template names the release and configuration your deployments should be on, and an Update Manager rule applies it on a schedule. Anyone with fleet read access can read templates, rules and history.
Before you start: both screens are under Fleet Management. Create the template first; New Update Manager Rule is disabled until one exists.
Create a Fleet Configuration Template
Open Fleet Configurations and click New Fleet Configuration Template.
| Section | Field | Values |
|---|---|---|
| Name, Description | Up to 100 and 500 characters. | |
| What this deploys | Deploys | Not set, Studio, or Minimal target stack (not Studio). |
| Environment | Not set, dev, staging or prod. | |
| Which release | Release version | "Versions from the AlphaAgent catalogue. A version is mirrored into your organisation the first time a job uses it.", such as "2.0.14 — stable — latest". |
| Sizing | Sizing profile | Automatic (blank), xs, small, standard, large, xlarge. |
| Redis node type | One your organisation offers, or a typed cache.<family>.<size> value. | |
| Inference zone | Blank, us or eu. | |
| Models | Sonnet model id, Opus model id | Blank for the shipped default, or a Claude 4.x id your organisation offers (Sonnet 4.6; Opus 4.6, 4.7 or 4.8). |
| Data protection | PII redaction default | Not set, Off, Mask or Hash. Workflows and runs can tighten it, never loosen it. |
| Front door | Applies to every deployment; not a template setting. |
The preview reads "This template will set N field(s)". Click Create. A template never carries an account, region, certificate or sign-in domain prefix; those belong to the deployment.
Edit opens the same modal; saving increments the template to version N+1, and a rule pinned to vN keeps applying vN until an admin adopts the new version. The list shows Name, Description, Version, Release, Rules and Updated. Delete warns when rules still use the template: they are stranded until pointed at another template.
A template is applied in two places: the deployment wizard's Start from a template section, where "<name> (vN)" pre-fills the draft and every field stays editable (Deploy your first Studio); and an Update Manager rule.
Create an Update Manager rule
Open Update Manager and click New Update Manager Rule.
- Name (up to 100 characters).
- Fleet Configuration Template: pick "<name> (vN)"; the rule pins that version.
- Deployments: tick the targets or Select all. The preview reads "This rule will affect N deployment(s)" and, per deployment, "<current release> → <target>" or "(already on target version)" plus any configuration difference (Sizing, Redis, Sonnet model, Opus model). A Redis change briefly fails over the cache; a sizing change restarts every service.
- Schedule: the builder offers Frequency (Daily, Weekly, Monthly), Day, Day of month (1 to 28) and Time (UTC) as HH:MM, and confirms the sentence with the next three firings. Advanced accepts
rate(<n> minutes|hours|days)or acron(...)with exactly five fields: minute hour day-of-month month day-of-week. - Maintenance window: tick Only fire during a maintenance window and set Start (UTC) and End (UTC) on the hour; the end is exclusive, a start after the end wraps past midnight, and a firing outside the window is deferred to the next one.
- Enabled: off until you tick it. Click Create.
Refusals name the rule broken: a missing name, template, deployment or schedule; a malformed rate or cron; an incomplete time; a window whose start and end hours are equal. A rule from an earlier release that used a filter shows a banner and switches to an explicit list on save.
The list shows Name, Fleet Configuration ("<template> (vN)" with Adopt vN when a newer version exists), Scope, Schedule, Maintenance window ("HH:00 to HH:00 UTC" or "Any time"), Enabled, Next run, Last run, and Edit, History and Delete. Adopt vN warns that matching deployments restart every service in one rolling upgrade, interrupting anything mid-flight such as a knowledge graph still building. Delete leaves deployments the rule already upgraded unaffected.
Read a rule's History
History shows one card per firing: Fired, Nothing to do, Drift found, not applied, Deferred (outside window), Template missing or Template edited, not adopted. A firing that started jobs lists "Triggered: <deployment> (<status>)" and any skips: "Skipped (paused)", "Skipped (job in flight)" or "Skipped (zone mismatch)". A deployment that keeps failing is flagged "has failed N job(s) in a row". Load more pages back.
What a roll does
When a rule fires and a target is off the template's release or configuration, it starts an Upgrade job on that deployment. The job runs preflight, captures a restore point, shows the Studio maintenance page to users, updates the core, re-seeds the model ids and configuration, pushes and verifies images, updates the web app, edge, stateless and compute stacks and the task definitions, waits for the services to settle, restores the normal Studio app, runs the doctor and records the new release. On a live walk a rule fired at its scheduled minute and rolled two Studios to the next release in 47 minutes, 17 steps each, with the maintenance page shown meanwhile. The Fleet's Version column reads "<current> → updating to <target>" throughout.
If an update fails after it has started, the job rolls the deployment back to its restore point and ends Rolled back; there is no rollback button. Three failures cover the edges, listed on Failure codes: no_restore_point, rollback_failed and restore_point_unwritable.
What you should see
- After a firing: an Upgrade job in each targeted deployment's Jobs view, the Fleet's Version column reading "<current> → updating to <target>", and History showing Fired with "Triggered: <deployment> (<status>)".
- When it finishes: every targeted row on the template's release, Healthy, with Last job pointing at the upgrade.
Notes
- Sizing profile, Redis node type and model ids are not editable on the deployment's Overview: save them in a template and point a rule at it, or adopt the new template version on an existing rule.
- To update one deployment straight away: create a rule scoped to that deployment with Advanced schedule
rate(5 minutes), no maintenance window, Enabled; History shows Fired within five minutes; disable or delete the rule once the Upgrade job has started. - A rule skips a paused deployment, one with a job in flight, and one whose inference zone does not match the template.
- Template edited, not adopted: click Adopt vN. Template missing: edit the rule and choose another template. Deferred (outside window): it tries at the next firing inside the window.
- The wizard refuses a template authored for an older form: re-save it from Fleet Configurations.