Upgrading a runner to a new version

CloudRadial AutomationAI publishes runner code as immutable, versioned packages, and you move an existing runner to a newer version with an upgrade script downloaded from the Runners page. This article covers the update-available indicator, running the upgrade, how it handles each hosting plan, and that it is idempotent and touches every instance. It is for the technician operating a runner.

• The Update-Available Indicator
• Download and Run the Upgrade
• How the Upgrade Works per Plan
• Every Instance, Idempotent

The Update-Available Indicator

The Runners page shows each runner's reported version and flags a runner whose version is behind the region's target version. When a runner is out of date, download its upgrade package from that page. The package is generated for that one runner and targets a specific version.

Download and Run the Upgrade

The upgrade package contains Update-AutomationsRunner.ps1 and an UPGRADE.md. It is credential-free and provisions nothing new — it only moves your runner's Function Apps to the target version's package. Your runner identity, secret, Key Vault, and networking are untouched. Sign in and run it:

Connect-AzAccount
./Update-AutomationsRunner.ps1 -SubscriptionId <your-subscription-guid>

-SubscriptionId is optional — omit it to choose from a numbered list of the subscriptions your login can access. Add -WhatIf first to preview, -TenantId <tenant-guid> if the subscription is in a non-default Entra tenant or you hit a multi-factor prompt, or -ResourceGroup <name> to scope the search. The script needs the Az.Accounts, Az.Resources, and Az.Websites modules, and the Function Apps must be able to reach the runner package store.

How the Upgrade Works per Plan

The script finds the runner's Function Apps by the identity tag the installer stamped on them, detects each app's hosting plan, and upgrades it the matching way:

• Premium — the app is repointed at the target package, its runtime stack is reconciled, and it is restarted
• Flex Consumption — Flex has no run-from-package, so the package is pushed to the app. Because the runner sits with no public access, its deploy endpoint is opened transiently for the push and re-locked afterward, even if the push fails

The agent flavor is always on Flex Consumption and is upgraded the same way as the script runners.

Every Instance, Idempotent

Every instance of a runner pool carries the same identity tag, so one upgrade run sweeps and upgrades all of them. The upgrade only moves the version and never changes the pool size — use the installer for scaling. On the next poll after the upgrade, each app reports the new version on the Runners page. Re-running the upgrade is safe: an app already on the target version is simply re-applied.