Skip to main content
Matillion will issue updated versions of the Maia runner on a cadence set by the version track described below. In addition to changes that are required to align with the Maia SaaS application, new versions will include bug fixes and security updates. Matillion-hosted Full SaaS deployments will always use the latest available Maia runner version. If you deploy a Hybrid SaaS Maia runner in your own infrastructure, you have some control over how you update the Maia runner as long as you are always using a supported Maia runner.
Matillion will not be able to guarantee support for older Maia runner versions, therefore we recommend that you always run the most recent Maia runner version which has been released on your version track. Version tracks are discussed below. Read Software updates and patch management for details of our support policy.

​
Version tracks

The Maia runner update cadence depends on whether you chose the Current or Stable version track when you created the Maia runner. Read Maia runner version tracks for a full discussion of version tracks. If you have auto update enabled, your Maia runner will be automatically updated to the latest version on your chosen version track as soon as it’s available. Without this option enabled, you will have to manually update to the new version. Critical security patches are only applied to the supported Maia runner releases on both tracks.

​
Release cadence

Maia runner releases are made on the following cadence:
  • Current track: Usually twice a week, typically on a Tuesday and Thursday, though this may vary. These releases may include new features, bug fixes, and security patches.
  • Stable track: Once per month, on the 1st of the month.
  • The Maia runner for Snowflake is updated once per month on the second Tuesday of the month.
If you need to change the track that an existing Maia runner is on, you can use the Update a Maia runner public API endpoint. However, take note of the following:
  • Changing the Maia runner‘s version track does not update the Maia runner itself. You must update the image URI for the Maia runner service in your cloud provider. If you don’t, the Maia runner version may show as “Out of support”.
  • If you change the Maia runner state from Current to Stable and update the installed Maia runner service, pipelines created using a newer (Current) Maia runner version might not run as expected on an older (Stable) version.

​
Auto update

By default, Maia runners are created to automatically update. However, you can opt out of this process.
If you opt out of automatic updates, ensure you have a manual update procedure in place. Read our Maia runner support policy. If you are using the Current track and wish to opt out then it may be prudent to use the Stable track instead due to the faster update cadence of the Current track.
The standard Maia runner installation uses a tagged container image on the container repository. This tag is always kept on the most recent released image for a given version track. If the Maia runner installation in your cloud infrastructure is set to always pull the latest version, then whenever a Maia runner instance is started, it will always pull this latest version. This means that whenever you restart a Maia runner, it will be automatically updated to the latest release on its version track, regardless of whether auto update is enabled or not. If your Maia runner has multiple instances, and one instance happens to be on a later version than another due to the timing of restarts, then the reported version of the Maia runner will always be the lowest version of any instance, and the availability of Maia features will be linked to that lowest version. If a Maia runner has auto update enabled, then whenever a new version is released on its version track (Current or Stable), the Maia runner will be automatically updated to that version. You can change a Maia runner‘s auto update status at any time from the Maia runner details screen. The auto update process will issue a graceful shutdown command to the Maia runner when a new version becomes available. This allows the Maia runner to finish the task it’s working on before shutting itself down. The Maia runner will then restart, and as part of the restart process will automatically update to the latest available version of the Maia runner. If auto update is not enabled, you will be notified when a new version is released, and must manually update the Maia runner. If a Maia runner falls behind the latest release on the version track because you have disabled auto update, and you then enable auto update, it will not immediately update itself to the latest available version. The Maia runner update will only be triggered when the next version is released on its version track, or if the Maia runner is restarted for any reason, in which case it will always update to the latest available version.

​
Snowflake

For update information about Hybrid SaaS Maia runners installed in Snowflake using the Native App, read Updating a Maia runner.

​
Manual update

If you haven’t enabled auto update, you will need to check whether a new Maia runner version is available on your version track. In the list of Maia runners, the text Update available is displayed below the Maia runner version number if a new version is available. Additionally, the latest available version number, version release date, and an update notification will be shown on the Maia runner details screen. To update the Maia runner manually, follow the process given in Restart a Maia runner. Restarting the Maia runner automatically updates it to the latest release on its version track, as long as the installed Maia runner is always pulling the latest image. If your Maia runner service isn’t configured to pull a new image on restart, you should use the pause Maia runner command to put your Maia runner into a safe state where it can be restarted manually from your cloud provider. You can also update the Maia runner from the runners API endpoint. The endpoint can also be used to determine whether a new Maia runner version is available. For further details on using the Maia API, read API overview.