Upgrading Exekra
Hub, Studio, and Runner are upgraded by running the latest installer in place. The installer detects the existing installation, stops the affected service if needed, applies the new version, and restarts. Data, configuration, and license are preserved.
Before you upgrade
- Check the Release notes for the version you are moving to. Note any breaking changes or migration steps called out for that release.
- Take a fresh backup of the PostgreSQL database and the Hub configuration directory (see Service management for what to back up).
- Schedule a brief Hub downtime window for the Hub upgrade.
- If you are several versions behind, read the release notes for each intervening version, not just the target.
Upgrade the Hub
Download the new Hub installer
Download the latest Hub installer from the Customer Portal.
Stop the Hub service
Run nssm stop ExekraHubService from an elevated terminal. Confirm with sc query ExekraHubService.
Run the new installer as Administrator
The installer detects the existing Hub, preserves your configuration, runs any required database migrations, and restarts the service.
Verify the dashboard loads
Browse to the Hub URL. Sign in and confirm runners reconnect within a heartbeat cycle.
If anything goes wrong, the previous Hub installation directory is preserved alongside the new one. The Hub can be rolled back by restoring the database backup and reinstalling the previous version.
Upgrade Studio
Studio is per-user and per-machine. Either:
- Download and run the latest combined Studio + Runner installer on the user's machine; or
- Let the in-app update prompt walk the user through the upgrade when the user next signs in.
No data is stored locally that needs to be preserved; Studio reads workflow definitions from the Hub.
Upgrade Runners
Each Runner machine runs the same combined installer. To upgrade a single Runner:
- From the Hub, mark the Runner as Draining so the queue worker stops assigning it new executions. Wait for any in-flight execution to complete.
- Run the latest installer on the Runner machine.
- The Runner reconnects to the Hub automatically using its existing credentials and returns to Online.
For larger fleets, upgrade Runners in batches so the platform is never below the concurrency you need for in-flight work.
Reference
- Release notes for the changes in each version
- Service management for the underlying service commands and log locations
- Troubleshooting if a Runner does not reconnect after upgrade
Was this page helpful?
A quick signal helps us prioritise improvements.