HarnessBuild

Versions, publishing and going live

Updated 2026-11-12

Every change to an Ailo is saved as an immutable package version. Customers always meet the live version; saving and publishing never change it, only going live and rolling back do.

Three actions #

Action Result Affects conversations?
Save a version A content item or setting gets a new version No
Publish The latest version of every content item is combined into a new package version No
Go live A package version becomes the live one Turns that start afterwards read it; turns already under way do not change

Rolling back is making an older version live again.

In the console #

Workspace › Release lists every version of each Ailo: version number, when it was saved and by whom, with "Live" and "Previously live" marked.

  • Members with console.publish see "Go live" on versions that are not live.
  • Members with console.deploy see "Roll back to version N", which returns to the previous live version.
  • The confirmation dialog shows which version the live one changes from and to, and which sites are affected.
  • Each version links straight to its run records.
  • The page reloads every 15 seconds and when you return to the tab, so a release made elsewhere shows up here.

Orbit can prepare going live and rolling back for you, but it only shows a confirmation card; you confirm.

Through the API #

Command or query HTTP CLI
list_packages GET /api/tenants/{tenant_id}/packages ailo packages
read_package GET /api/tenants/{tenant_id}/packages/{package_id} ailo packages show P
list_package_versions GET /api/tenants/{tenant_id}/packages/{package_id}/versions ailo packages versions P
set_package_live_version POST /api/tenants/{tenant_id}/packages/{package_id}/commands/set_package_live_version ailo packages live P N --expected-revision R
rollback_package_version POST /api/tenants/{tenant_id}/packages/{package_id}/commands/rollback_package_version ailo packages rollback P --expected-revision R
  • Package commands must carry a command_id; retrying with the same command_id returns the first result and never runs twice.
  • Read expected_revision from read_package. If someone changed the package in between, you get 409 revision_conflict; read again and retry.
  • Publishing content (publish_content) and full request and response examples are in Knowledge and SOP API.

Checks before going live #

When a version goes live, the platform checks it against every site that runs the package and keeps the current live version if anything fails:

code When
sop_tool_missing A tool some SOP needs is missing on the site, or not turned on for Ailo
too_many_resident_tools The tools given to the model from the start, not declared by any SOP, exceed the platform limit (20 by default)
invalid_engine_config The version's engine parameters cannot be read
no_previous_version Rolling back with no previous live version

Which settings travel with a version #

A package version holds what belongs to the Ailo itself: the system prompt, SOPs, FAQ, tools, engine parameters, and whether each capability (handoff, assist tickets, knowledge search and so on) is on for each site. All of these take effect when it goes live and go back when it is rolled back.

Models are not in the package version; they come from the organization's settings.

When the Ailo serves a channel of another Desk organization through a connection, Desk's settings are not in the package either: the handoff switch and mode, business system bindings and credentials, business hours, wording and so on all come from the Desk site. Writes and confirmations are capped by the Desk site; the package can only narrow them.

Next #