Pack Version Management
View installation state across all content kinds, review workflow impact, and update packs from the Packs catalog page.
The Settings → Platform → Packs → Catalog tab is the single place to track which version of each pack is installed, see per-content-kind install state, and apply updates. For the full versioning model from a pack author's perspective — semver rules, the release checklist, and how pins/policies decide what runs — see Pack versioning. The Add Integration marketplace shows a badge and a link when a pack integration has an update available — updates always run from the Packs page.
Seeing where a pack is used
The catalog table's In use column shows what each installed pack actually produced in your organization:
- Workflows — workflows deployed from the pack, per workspace environment. Click a workflow to open it in Agentic.
- Process flows — live process-flow instances created from the pack's templates. The count is the true total; the popover lists the 25 most recent. Click an instance to open it in Agentic.
- Data sources — data sources installed from the pack. Click to open the data sources page in Analytics.
A dash (—) means the pack is in your catalog but nothing currently uses it — a useful signal before retiring a pack.
Expanding a pack row shows the same information in detail, plus Workflows using this pack's integrations: workflows anywhere in your organization whose blocks call an integration this pack installed. This is the same impact analysis the update flow runs — shown at all times, so you can assess blast radius before retiring or updating.
If a panel shows State unavailable, one backing service could not be reached; the other panels remain accurate.
Install State Column
Each row in the Catalog tab shows one pack at its highest available version. The Install state column shows the most important state across all of that pack's content kinds:
| State | Meaning |
|---|---|
| Update available | At least one content kind has a newer version in the catalog than what is currently installed. |
| Installed | All installed content kinds are current (no update needed). |
| Not installed | No content from this pack has been installed in your organization. |
When an update is available, the version column shows the installed version alongside the latest: for example v1.1.0 → v1.1.1.
Expanded Row — Per-Kind State
Click any row to expand it and see the install state broken down by content kind:
Integrations
One line per vendor included in the pack. Shows the installed version and whether an update is pending. The update check is based on the artifact hash: if the published artifact differs from what is installed, an update is available.
Ontology and KB Domains
Shows the installed pack version and the date it was last applied. These content kinds apply org-wide at install time.
Workflows
Shows one row per workspace environment in which this pack's workflows have been deployed. Each row includes:
- The workspace environment name.
- The installed pack version, or version unknown if the workflow was deployed before version tracking was introduced. "Version unknown" is harmless — the workflow is running, but its pack version cannot be compared.
Deploying a workflow to a workspace is a separate action in the Marketplace. The Packs page shows workflows that were already deployed; "not deployed" environments are omitted from the list.
Data Sources
Shows one row per workspace environment in which a data source from this pack is installed. Installation and configuration of data sources happens in the Analytics app's data-sources settings.
Process Flows
Process flows always track the latest catalog version — they do not have a fixed installed version. The expanded row shows a badge confirming this. There is no update action for process flows; they automatically use the content from the newest active catalog row for this pack.
Updating a Pack
When at least one content kind has an update available, an update bar appears at the top of the expanded row.
Click the pack in the Catalog tab to open the expanded view. If there is an update available, the update bar shows the target version (for example, Update to v1.1.1) and a summary of which integrations will be affected.
For packs that include integration content, the platform automatically loads a workflow impact analysis — showing which workflows reference tools from this pack's integrations. The Update pack button stays disabled until this analysis has finished loading.
If the impact analysis fails to load, the Update pack button remains disabled. Check your network connection or contact your platform administrator.
The platform diffs the installed and target integration manifests and lists detected breaking changes directly in the update bar: removed tools, new required inputs, changed input/output types, or auth-mode changes — each annotated with the tool it affects.
Two warning levels can appear:
- Potentially breaking (amber) — the update is a major version bump, or the manifest diff found breaking changes that the author declared correctly.
- Breaking changes in a non-major update (red) — the manifest diff found breaking changes but the version bump is only a minor or patch. Treat this with extra care and contact the pack author.
Review the affected-workflows list together with these findings before proceeding.
The platform installs the latest catalog version for this pack. All content kinds are updated together — integration, ontology, workflows deployed in each environment, and data sources. A success toast confirms the update.
Clicking Update pack also moves your organization's version pin for the pack's integrations: in-flight workflow runs finish on the version they started with, and new runs use the updated version.
Version Pinning and Update Policies
Installed integration versions are pinned per connection. A newer version arriving in your catalog (for example via a Git pack source sync) is staged but inert — nothing changes about what your workflows execute until the pin moves. The pin moves in one of two ways:
- Manually — you click Update pack after the impact review (the default for every connection).
- Automatically — a connection can opt in to auto-updates via its update policy:
| Policy | Behavior |
|---|---|
manual (default) | Updates are staged only; you apply them from the Packs page. |
auto_patch | Patch releases (1.1.0 → 1.1.1) apply automatically when the manifest diff finds no breaking changes. |
auto_minor | Patch and minor releases apply automatically when the manifest diff finds no breaking changes. |
Auto-updates never apply when the manifest diff detects a breaking change — the connection is flagged (update blocked: breaking_diff) and the update waits for your manual review on the Packs page. Major version bumps always require a manual update.
SDK Compatibility Errors
Integration bundles are compiled against a specific version of the Scrydon authoring SDK. If a bundle was built against an SDK contract the platform no longer (or does not yet) support, you will see:
- At install time: the pack install fails with
integration_contract_incompatibleand a message naming the contract versions involved. - At run time: tools from the bundle fail with
BUNDLE_CONTRACT_INCOMPATIBLEinstead of executing.
Both messages mean the same thing: the bundle needs to be republished with a current @scrydon/sdk-authoring release. If you author the pack, rebuild it with the latest SDK and publish a new version; if it comes from a vendor, ask them for an updated release. Bundles built against the immediately previous SDK contract continue to work — the platform translates for them automatically.
Other Live Catalog Versions
At the bottom of the expanded row, Other live catalog versions lists any older versions of this pack that are still present in your catalog (for example, if a previous version was installed and the catalog was not cleaned up). These entries are informational — they show what is available but are not the active installed version.
Finding Updates for Integrations in the Marketplace
When a pack integration has an update available, its card in Settings → Platform → Integrations → Add Integration shows an Update badge instead of the usual status. Clicking the card or its action opens Settings → Platform → Packs with the relevant pack pre-selected so you can review the impact and apply the update there.
Integrations that are already installed and current show a Up to date indicator in the From your pack catalog group. They remain visible so you can open the vendor configuration without navigating away from the marketplace.