Skip to content

Tech note July 2025: agent updating and support

As of September 23rd, Matillion will be introducing some changes to better reflect the support policy for hybrid agents, as laid out in our Agent version support policy.

What you should expect to see:

  • Additional indicators in the agent manager screens to highlight any agents in need of attention.
  • Unsupported agents may be unselectable when creating new project objects such as schedules or environments.

Note

Existing schedules and published pipelines will continue to function.


Why is this important?

  • Uninterrupted support: To ensure we can provide the most effective and efficient support, we will typically ask you to upgrade your agent to a supported version before we begin troubleshooting any ongoing issues. Keeping your agent up to date helps us investigate issues without delay.
  • Access to New Features: New features and enhancements to the Data Productivity Cloud are designed to work with supported agent versions. Using unsupported agents may result in newly created or saved pipelines failing to execute.

What should I do?

If you use automatic updates

Check that your agents are currently updating. You can check this by going to Manage agents (or using the public API) and seeing if there is an Update available message. If so, check the agent details and see if this is just a minor delay due to a currently rolling-out update, or if you have an automatic updating issue.

If you manage updates manually

Check that your updates are being applied, making the same check as above. If you see an obvious version lag, then speak to whomever in your organization manages your infrastructure to ensure that adequate provisions are made to check the latest updates are being applied.

Note

The Current track will update more than once a week, whereas the Stable track will update on a monthly cadence.


Still unsure?

Read Agent updates, and if you have any questions, contact support for assistance.

Note

If using AWS ECS, you may have been affected by AWS changes to the service. In this case, this tech note has more information.

Got feedback or spotted something we can improve?

We'd love to hear from you. Join the conversation in the Documentation forum!