Great news! Our validation UX improvements are now generally available. These enhancements make pipeline development faster and more efficient by removing previous limitations.

✅ What's new

• Keep building while validation runs: Move on to the next component as soon as it's validated, rather than waiting for the whole pipeline.
• No more validation timeouts: Validations that used to hit the 2-minute cap now run through to completion, however long they take.
• Cancel long-running validations: Cancel directly from Designer whenever you need to.

These improvements mean you can work more efficiently without being blocked by lengthy validation processes, giving you better control over your development workflow.

For a full list of recent changes, be sure to check our changelog updates.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Want to get involved?

Join the Matillion Community to stay up to date, share feedback, and help shape our product roadmap for future innovations.

This week, we're focusing on making your Maia experience smoother and more efficient. We've made major upgrades to Convert Workloads that prioritize accuracy and transparency.

🔄 Convert Workloads improvements

We've enhanced how Convert Workloads runs so that it prioritizes correctness and delivers more accurate results. Here's what's new:

• Workloads are now preprocessed to remove noise, with the cleaned version written to your branch so Maia Team can review the source workload for debugging if needed.
• A new self-review step double-checks all analysis after processing is complete.
• Detailed progress reporting keeps you updated in real time as Convert Workloads progresses through each analysis stage.

To get started, read Convert workloads from other platforms.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

This week, we're excited to bring you powerful updates that enhance collaboration and give you greater control over your development workflow. From redesigned branch management to granular permissions and expanded API capabilities, these features are designed to make your Maia experience more flexible and efficient. Check out the full changelog updates for more details.

🌿 Redesigned branch management

The branches experience has been overhauled to give you more control and visibility over your work.

• The branches page now features new columns giving you more information at a glance, with your default branch pinned to the top of the list for quick access
• Remote branches created directly in your Git repo are now automatically visible in your branch list, so your view is always in sync
• A new merge modal lets you merge from either remote or local branches
• You can create and delete your own branches independently—without sharing them with the whole team or affecting your teammates' work—and clear warnings now surface before any destructive action that could result in lost work
• Environment choice is optional while creating branches. You can now select the environment you want to work on within Designer

Note: delete is an action that cannot be undone

Read the documentation to learn more about the enhanced branch management capabilities.

🏃 Runner management granular permissions

In anticipation of customer roles, granular permissions for runner management are now live.

What's new?

Before, runner management was behind a global manage runners permission. Now, aspects of runner management are governed by specific permissions. Want to give someone permission to edit an allow list without letting them change anything else? Now you can.

How do I use it?

At the moment, these permissions apply to the pre-provisioned roles. Once custom roles are released, you'll be able to create your own roles with the runner permissions you select. This also applies to any public API credentials.

Learn more about account roles in the documentation

💻 Additional connections API endpoints now available

We're also introducing two new API endpoints:

• GET SCHEMA: Retrieve the relevant format for each connection provider, so you can programmatically and dynamically structure your connection requests. For more information, read Get Connection Schema.
• TEST CONNECTIONS: Test a given connection on a specified environment, so you can create and test new environments or test connections as part of your CI/CD pipelines. For more information, read Test a Connection.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Head over to the Matillion Community to share your comments and questions.

This week, we're excited to unveil a major infrastructure upgrade with the launch of our new connections model. For a full list of recent changes, read our 2026 changelog.

🔗 Connections make credential management easier than ever

We've launched a new connections model that replaces the existing split between Secret definitions, OAuth, and cloud credentials. Instead of storing just the sensitive part of a credential, a connection stores the whole thing: URL, username, and secrets as a single reusable object.

This means:

• Reusability and portability: change a connection once, and it updates everywhere it's referenced
• Environment-specific properties: vary connection properties by environment without using project variables
• Consolidated management: Secret definitions, OAuth, and cloud credentials are now managed from a single Connections tab

We've also shipped the ability to create any type of connection—new or legacy—inline in Designer, so you can add your credentials without leaving your pipeline.

Important info:

• Gradual rollout: not every component supports the new model on day one. Support is being added component by component. Components that have been updated show a Connection field in their config panel.
• Existing pipelines keep running: your published pipelines will continue to run as normal. The next time you open a pipeline in Designer, upgraded components are automatically backfilled with the [Legacy connection] option so they keep working when you next publish.
• No forced migration: if a component supports the new model but you'd rather use your existing credentials, just select [Legacy connection] from the dropdown.

Read the full documentation for complete details on what's changed and frequently asked questions.

This week, we're excited to bring you powerful updates that enhance your control and efficiency within Maia. From improved Designer functionality to smarter task management in Mission Control, these features are designed to streamline your workflows and give you more precision in how you work. Check out the changelog updates for full details.

⏪ Undo and redo improvements in Designer

You can now undo and redo changes from any panel in Designer, with no risk of confusion between undoing work on the canvas or in a panel. In addition, pipeline validation no longer re-runs after you undo cosmetic-only changes, such as moving a component or editing a note.

This means you can confidently undo from anywhere in Designer—the variables panel, component properties panel, or the canvas—without needing to refocus. Skipping validation when you undo a minor change saves unnecessary processing time and lets you continue building pipelines efficiently.

🚩 Task priorities in Mission Control

You can now set a priority level for each Mission Control task—High, Medium, or Low—to control the order in which Maia Team works on them.

When you queue up a backlog of work, not everything is equally urgent. Use task priorities to tell Maia Team what matters most, so your important tasks are always picked up first.

What's new:

• Set a priority level: Choose High, Medium, or Low priority when creating or editing a task.
• Smarter backlog ordering: Tasks in your backlog are automatically worked on by priority, highest first. When priorities match, the oldest task goes first—so nothing gets buried.
• Filter by priority: Use the filters on the Mission Control board to focus on just High, Medium, or Low priority tasks.

Read the Auto-start section of our Mission Control documentation to learn more about task priorities, or check out our guide to Tasks in Mission Control to find out how to set a task’s priority level.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Welcome back to the Maia New Features Blog! This week, we're excited to introduce the Upgrade Assistant, a powerful new tool designed to streamline your migration experience and make transitioning to Maia smoother than ever.

✨ Migrate to Maia with our new Upgrade Assistant

We're excited to announce the Upgrade Assistant, a powerful new tool within Maia that simplifies and streamlines the migration of Matillion ETL workloads.

This new feature lets you connect Maia directly to your existing Matillion ETL instances, which makes it easier and quicker to migrate your workloads to Maia. With the Upgrade Assistant, you can:

• Migrate schedules, jobs, secret references, shared jobs, API Extract profiles and API Query profiles
• Configure advanced import options, including migrating Python workloads to Script Pushdown components
• Create custom connectors automatically from API Extract profiles
• Migrate shared jobs without needing to create custom mapping documents

Ready to get started? Check out the Upgrade Assistant documentation!

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.